Posts

Showing posts from July, 2022

How to Disable or Delete your Facebook Account

Image
If you'd like to disable or delete your  Facebook  account on a desktop machine you can simply go to this URL https://www.facebook.com/deactivate_delete_account Or follow these steps. Logon to Facebook Click your image in the top right and select Settings & Privacy Select Settings Select Privacy Select Your Facebook Information Select Deactivation and Deletion You can then decide which action to take NOTE: One of the issues with Facebook is that once you've disabled your account if you use Facebook authentication to login to a third party site like AirBnB or Meetup your account will be re-enabled. If Facebook is going to continue with offering authentication services then they really need to be forced to separate their authentication services from their Facebook profile.

Issue with Get-NetFirewallProfile PowerShell cmdlet and netsh advfirewall command incorrectly displays Windows Defender Firewall state when configured with Group Policy

Image
When running either the  Get-NetFirewallProfile PowerShell cmdlet or netsh advfirewall command you may find they incorrectly display thee Windows Defender Firewall enabled state when the firewall is configured with Group Policy. By default the Windows Defender Firewall is on Disabling the firewall in the MMC displays as expected in the summary pane Both netsh and PowerShell's  Get-NetFirewallProfile  correctly show the state as disabled. However when the firewall's Domain profile is disabled using Group Policy You see that the user interface again updates correctly, and a message stating that Group Policy is in force However, BOTH  PowerShell and netsh incorrectly report the Firewall as being enabled. The registry key backing this configuration is HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\WindowsFirewall\DomainProfile DWORD Enabled  Running Process Monitor from sysinternals  it doesn't appear that either PowerShell or Netsh are looking at the group policy setting. The

Compex SP device won't charge with the screen flashing and "Check..." shown on the screen.

Image
If you have Compex SP device that won't charge with the screen flashing and "Check..." shown in the top right of the screen, it's not good news. These devices are so very expensive and yet there seems to be an issue that the batteries will completely fail even when the device isn't in use and stored away in its box. You can contact Compex support but they'll just insist you to hand over another £39.68  (with shipping) for what is essentially 4 rechargeable batteries glued to a plastic cover. https://www.compex.com/uk/spare-battery The solution. Hand over your money or throw the thing in the bin.

When using the Azure Az PowerShell cmdlets you receive the error "Disable-AzContextAutosave : Key not valid for use in specified state."

When using the Azure Az PowerShell cmdlets you receive the error "Disable-AzContextAutosave : Key not valid for use in specified state." This can be caused by a problem with the file  %LOCALAPPDATA%\.IdentityService\msal.cache Renaming the file msal.cache to msal.cache.old seems to resolve this issue.

When using the GetSecurityDescriptor method of the StdRegProv class you receive unknown error (0x8004101d)

Image
We've recently had an issue using the GetSecurityDescriptor method of the StdRegProv class you receive unknown error (0x8004101d). This appears to be a limitation in the WMI provider when there is an unresolved account in the security descriptor / ACL. You can replicate the issue by  Creating a local user account Assigning this user account to a registry key Close regedit Delete the local user account Reboot You will now seen an unknown account referenced, which will cause the issue with the  GetSecurityDescriptor  method. To resolve the issue you need to remove the unresolved account from the ACL, or use the an alternative method of collecting the information such as the Get-Acl PowerShell cmdlet.   While you're here - Why not check out our Windows Server Documentation and Audit Tool?

When using PowerShell Get-WinEvent cmdlet you receive the error "Get-WinEvent : The specified resource type cannot be found in the image file"

Image
When using PowerShell Get-WinEvent cmdlet you receive the error "Get-WinEvent : The specified resource type cannot be found in the image file" This error isn't actually caused by the cmdlet, but occurs when the event log cannot resolve the text for the error. The error can be safely ignored Get-WinEvent -MaxEvents 1 -FilterHashTable @{ LogName = "System"; ID = 1001 } -ErrorAction SilentlyContinue The message is then returned as  Cannot retrieve event message text  however the rest of the properties are available.