Sage 100

Has anyone found an easy fix or permanent fix for Windows Updates breaking Paperless Office (Printer Not Activate -30). I'm going to suggest turning off Auto Updates and scheduling them along with wksetup reinstall, but not sure that's a good solution from a Windows Security Standpoint. Thoughts?

Are you referring to the Windows10 issue where you have to reset the Permissions in regedit? If so, it might be worth just giving the client the instructions.

I haven't had any issues with Windows 10 updates after changing the registry permissions. I would do that and see if it sticks otherwise like Brett says. Send them instructions. It might be something in a GPO causing it to change after Windows update.

the -30 Not Activated is not always because there is a problem with the Driver. A lot of times its because of latency. The PDF Converter is on a timer. If Sage does not respond in time the error occurs. The user clicks on OK. That PDF is not created and Sage moves on to the next one. IF, it happens immediately then from Sage KB search ""Quick PDF"" That should bring up my article that will so you how to remove, configure PDF converters by default.

What I have noticed in the past is that the Windows updates assigns One-Note to the NULL port which is the default port for Sage's PDF writer. Even if you delete One-Note, the Windows update will put it back and attach it to the NULL Port. The only solution to that is the creation of a Sage Port and attach the Sage PDF Converter to that Port. If that change already exists and you are still having issues I would (per @Brett & @George) look into the permissions being changed after the update. As you are thinking, turning off the automatic update and running them manually may help serve as a trouble shooting procedure.

Thanks Everyone, I'll give these a try!

Our most common problem with Windows Updates is the ""cannot process the lockfile"" error... with the user permissions to this key (attached) being reset. Emailing instructions on how to fix is easy enough, but yesterday we ran into a user where HKCC was entirely blank for a user, even when starting regedit as admin, so right-clicking on software and giving Users full control was not possible. There has to be a way Sage can store this information in some other location, so WU's don't cause this problem.