In this post, I describe a quick way to create a checksum in Windows using the free GUI tool 7-Zip. Checksums can be used to verify the integrity of files.  It can be useful to generate them when you are sharing files with others so they can check the file they receive hasn't been tampered with or corrupted. Resolution To create a checksum in Windows: 1. Download and install the free tool 7-zip EDIT: 2. In 7-Zip v24, right click the file you want to generate a checksum for, go to 7-Zip then  CRC SHA  then  * (In earlier versions of 7-Zip, go directly to  CRC SHA then  * ) 3. After a short time, the checksum is generated: 4. You can shift select all the rows and press CTRL-C to copy the information. This post has been edited.  Thanks to the comment below for pointing out the difference in the context menu in the newer versions of 7-Zip. Related Posts - Bulk rename Windows files with touch-friendly PowerRename

This post describes how to fix the error: Windows cannot delete object LDAP://... because: A referral was returned from the server. Cause This error occurred when I was trying to delete a domain controller using Active Directory Sites and Services.  The domain controller was part of a child domain which I had demoted. Resolution I force deleted the server using ADSIEdit: 1. Open  ADSI Edit . 2. Right click the  ADSI Edit  root node in the tree view on the left then select  Connect to... 3. In  Connection Settings , change the  Naming Context  to  Configuration  then press  OK 4. Navigate down to  CN=Servers  then right click the server you want to delete and select  Delete Related Posts - The time between replications with this source has exceeded the tombstone lifetime - The operation failed because spn value provided for addition/modification is not unique forest-wide - Error 0x2015(The directory service can perform the requested operation only on a leaf object.) - Group Policy Audit

This post describes how to fix the error: “DsRemoveDsDomainW error 0x2015(The directory service can perform the requested operation only on a leaf object.)” and “ldap_delete_ext_sW error 0x42(66 (Not allowed on Non-leaf). Ldap extended error message is 00002015: UpdErr: DSID-03100E01, problem 6003 (CANT_ON_NON_LEAF), data 0 Win32 error returned is 0x2015(The directory service can perform the requested operation only on a leaf object.))” Cause There errors can occur when you use ntdsutil metadata cleanup or partition management and you try to delete domains or partitions that are not leaf objects i.e. objects that have children. They occurred for me when I was trying to delete a child domain before deleting domaindnszones. Resolution To resolve this issue, delete the child objects that are children, before attempting to delete their parents. 1. Run ntdsutil 2. Enter  partition management 3. Enter connections 4. Enter connect to server %ServerName%  (replace with your DC server name) 5

This post describes how to fix the error: The operation failed because spn value provided for addition/modification is not unique forest-wide Cause This error occurred when I demoted a child Active Directory domain controller then tried to rejoin the parent domain.  I think the parent domain still had some record of the SPN which I was not able to delete.  By default, Windows checks to ensure the SPN is unique. Resolution To resolve this issue, I disabled the uniqueness check as follows: 1. Open  ADSI Edit . 2. Right click the  ADSI Edit  root node in the tree view on the left then select  Connect to... 3. In  Connection Settings , change the  Naming Context  to  Configuration  then press  OK 4. Navigate down to  CN=Windows NT  then right click  CN=Directory Service  and select  Properties 5. Double click dSHeuristics and change the value to  000000000100000000023 to disable the UPN and SPN uniqueness checks. More information:  https://support.microsoft.com/en-us/topic/duplicate-spn-ch

This post describes how to fix the error: "The directory service cannot replicate with this server because the time since the last replication with this server has exceeded the tombstone lifetime." and "It has been too long since this machine last replicated with the named source machine. The time between replications with this source has exceeded the tombstone lifetime. Replication has been stopped with this source." Cause This error can occur when trying to replicate configuration to or from the selected DC in Active Directory Sites and Services when replication has not occurred for more days than is specified in the tombstone lifetime. This error can also be seen when running DCDIAG /v /q /a from a Command Prompt. Resolution Increase Tombstone Lifetime If you are using a test environment, you may not care if replication has not occurred for a long time, so you can resolve this issue by increasing the tombstone lifetime. To do this: 1. Open ADSI Edit . 2. Right cl

This post describes how to fix the error: There was a problem You cannot delete a sheet with a linked form. Please unlink the form first. Cause This can occur if you have created a new form which is automatically linked to the sheet. I did this accidentally when I was trying to go to Data -> Sort Sheet. Resolution To resolve the issue, go to Tools -> Manage form -> Unlink form: You should now be able to successfully delete the form: Related Posts -  Insert multiple rows above or below in a Google Sheet

This post describes how to resolve: WARNING: MSG:UnableToDownload «https://go.microsoft.com/fwlink/?LinkID=627338&clcid=0x409» «» Cause This warning can occur when trying to get a PowerShell repository and Tls12 is not specified as the SecurityProtocol. Resolution To resolve this issue, set the SecurityProtocol to Tls12 by running this command in PowerShell: [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 You should then be able to get repositories and install PowerShell modules successfully. Related Posts -  Unable to find package provider 'NuGet'. It may not be imported yet. Try 'Get-PackageProvider -ListAvailable'.

This post describes how to fix the error: PackageManagement\Get-PackageProvider : Unable to find package provider 'NuGet'. It may not be imported yet. Try  'Get-PackageProvider -ListAvailable'. At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:7415 char:30 + ... tProvider = PackageManagement\Get-PackageProvider -Name $script:NuGet ... +                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + CategoryInfo          : ObjectNotFound: (Microsoft.Power...PackageProvider:GetPackageProvider) [Get-PackageProvi der], Exception     + FullyQualifiedErrorId : UnknownProviderFromActivatedList,Microsoft.PowerShell.PackageManagement.Cmdlets.GetPacka geProvider Install-Module : NuGet provider is required to interact with NuGet-based repositories. Please ensure that '2.8.5.201'  or newer version of NuGet provider is installed. At line:1 char:1 + Install-Module -Name AzureAD + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + CategoryInfo 

This post describes how to fix the error: PackageManagement\Install-PackageProvider : No match was found for the specified search criteria for the provider  'NuGet'. The package provider requires 'PackageManagement' and 'Provider' tags. Please check if the specified package  has the tags. At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:7405 char:21 + ...     $null = PackageManagement\Install-PackageProvider -Name $script:N ... +                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + CategoryInfo          : InvalidArgument: (Microsoft.Power...PackageProvider:InstallPackageProvider) [Install-Pac kageProvider], Exception     + FullyQualifiedErrorId : NoMatchFoundForProvider,Microsoft.PowerShell.PackageManagement.Cmdlets.InstallPackagePro vider PackageManagement\Import-PackageProvider : No match was found for the specified search criteria and provider name  'NuGet'. Try 'Get-PackageProvider -List

This post describes how to resolve: WARNING: Unable to download the list of available providers. Check your internet connection. Cause This warning can occur when trying to install a PowerShell module or register a PowerShell repository and Tls12 is not specified as the SecurityProtocol. Resolution To resolve this issue, set the SecurityProtocol to Tls12 by running this command in PowerShell: [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 You should then be able to register module repositories and install PowerShell modules successfully. Related Posts -  WARNING: Unable to download from URI 'https://go.microsoft.com/fwlink/?LinkID=627338&clcid=0x409' to ''.

This post describes how to resolve: WARNING: Unable to download from URI 'https://go.microsoft.com/fwlink/?LinkID=627338&clcid=0x409' to ''. Cause This warning can occur when trying to install a PowerShell module or register a PowerShell repository and Tls12 is not specified as the SecurityProtocol. You can check the SecurityProtocol by running this command in PowerShell: [Net.ServicePointManager]::SecurityProtocol Resolution To resolve this issue, set the SecurityProtocol to Tls12 by running this command in PowerShell: [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 You should then be able to register module repositories and install PowerShell modules successfully. Related Posts - Get-PSGalleryApiAvailability : PowerShell Gallery is currently unavailable. Please try again later.

This post describes how to fix the error: Get-PSGalleryApiAvailability : PowerShell Gallery is currently unavailable.  Please try again later. At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:4264 char:9 +         Get-PSGalleryApiAvailability -Repository $Name +         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~     + CategoryInfo          : InvalidOperation: (:) [Get-PSGalleryApiAvailability], InvalidOperationException     + FullyQualifiedErrorId : PowerShellGalleryUnavailable,Get-PSGalleryApiAvailability Cause This error can occur when trying to set a value for a registered module repository and Tls12 is not specified as the SecurityProtocol. You can check the SecurityProtocol by running this command in PowerShell: [Net.ServicePointManager]::SecurityProtocol Resolution To resolve this issue, set the SecurityProtocol to Tls12 by running this command in PowerShell: [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12 You