This issue initially appeared in 2009 with the release of Windows 7. The same issue occurs when upgrading from Windows 10 to Windows 10 Anniversary Edition released in July 2016. The symptoms, the cause and the resolution are the same.
When upgrading from Windows XP or Windows Vista to Windows 7, or from Windows 10 to Windows 10 Anniversary Edition, you might receive error code -20 when trying to save a document to PDF for archiving or emailing. This issue happens with the developer version of Amyuni PDF Converter and only after an operating system update, it does not occur during a fresh installation of Windows.
Cause of this issue:
Windows 7 and Windows 10 Anniversary Edition do not update the HKEY_CURRENT_CONFIG\Software registry key. Amyuni PDF Converter uses this key to store its internal settings and fails after an operating system update.
Note: All options described below require Administrator access to the system)
Option 1) Reinstall the Amyuni PDF Converter Printer Driver, this will restore the security settings under this key and allow PDF Converter to continue using it.
Option 2) Follow the steps below to change the registry settings:
- Click on the Start button and enter "regedit" in the Search area, but do NOT hit Enter.
- You should see Regedit.exe at the top of the search results, right-click on it and select "Run As Administrator":
- Go to the end of the registry, open the HKEY_CURRENT_CONFIG key, right-click on Software and select Permissions:
- Make sure the "Full control" permission for the "Users" user is checked as in the screenshot:
Click OK, close the registry editor, and try saving your documents to PDF from your favorite application.
Option 3) Courtesy of Shawn K. Hall from SaferPC: Use a PowerShell script that will automate the process of adding the Users group with Full Control to the appropriate registry key
$acl = $key.GetAccessControl()
$rule = New-Object System.Security.AccessControl.RegistryAccessRule("Users","FullControl","ObjectInherit,ContainerInherit","None","Allow")
The PowerShell script can also be executed inline:
PowerShell.exe -NoProfile -NoLogo -NonInteractive -Command "$key = [Microsoft.Win32.Registry]::CurrentConfig.OpenSubKey('Software',[Microsoft.Win32.RegistryKeyPermissionCheck]::ReadWriteSubTree,[System.Security.AccessControl.RegistryRights]::ChangePermissions); $acl =$key.GetAccessControl(); $rule = New-Object System.Security.AccessControl.RegistryAccessRule ('Users','FullControl','ObjectInherit,ContainerInherit','None','Allow'); $acl.SetAccessRule($rule); $key.SetAccessControl($acl);"
Note: In order to run PowerShell, the logged in user will need elevated privileges.
This forum contains a series of Technical Newsletters designed to share with our customers valuable information about implementing or using our products.
1 post • Page 1 of 1