Sage 100

Upgraded customer from Standard 2015 to Advanced 2018. 1 user ""A"" is getting an Error when logging into Sage: Error: ""Sage.ERP100.Launcher.Bootstrap has stopped working"". It seems to be a Windows User Specific error. If User A logs into his own machine and then into Sage, he gets error. If User B logs into same machine (windows), User A can log into Sage successfully. If User A logs into another machine (windows), and then into Sage, he gets the error. Nobody is admin on their local machines and UAC is turned on high. IT is hesitant to create a new windows profile, something to do with Office 365? Resolution is to replace Launcher.Old.Exe if missing and if machine specific to do a repair on .Net (which I did). Any other ideas out there? These are Window 7 machines. .Net is 4.7.2. I uninstalled wksetup, turned off UAC (under my admin profile) and installed wksetup again, no change.

A total WAG. Ask IT if User A has a roaming profile and if so whether the Wkstn Setup location for User A is following them to whichever machine they log into. IOW the missing Launcher.Old.exe is following User A. Long shot I know.

Just encountered this on a new ROR account. NOT impressed with the prior resellers installation skills....

In my case, IT is creating a new profile. Did all the testing of creating a local user and it worked just fine, uninstalled everything, installed again as Administrator, same problem with the 1 user. Convinced IT it was not a Sage issue.

@NancyHanson - Any word yet from IT. My IT suggested that I install client on my local workstation and connect via the VPN. Umm, no! He has been charged with doing steps 2-4 from the KB. Can't wait to hear that that doesn't work.