Hello Chris,

Is it still there? I noticed when I did the update on a Test server the update was still in the Sage advisor update, but I was unable to really look at it at the time, but later that same day, I went back to look and the update was gone.

~Delray

Is the Client installed on that server?

Then what is the CurrentVersion at HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Best Software\FAS 100(or 500) Asset Accounting Client

Then in C:\SFAServ\COMMON There are some XML Document files Sage.US.SBS.SFA.<product>.XML. What is the <VersionId> in those files?

If it is not 20202.1.1, then editing and saving the file and the SAU should, eventually, clear the update.

If it is 2020.1.1, I would probably look to the firewall as blocking it from clearing somehow. Not sure how, or if it is a firewall issue how the update got there to start.

~Delray

That appears to be just one of those oddball things. There are only two places that the SAU is looking to see if you are up-to-date. On occasion, the Registry fails to update properly but there are tons of reasons why a write will not happen to the registry as expected. I have never seen those files not update properly.

~Delray

It's still there. 

Yes, the client is installed on the server. 

Current version in the reg reads 2020.1.1

Sage.US.SBS.SFA.Premier 2020.1

Sage.US.SBS.SFA.PremierClient 2020.1.1

Sage.US.SBS.SFA.PremierDepreciationClient 2016.1

Sage.US.SBS.SFA.PremierDepreciationServer 2016.1

I edit the xml file and recheck for update. The update is gone! Hopefully this is a bug?

Thank you for your help!