I haven't had the update but someone else mentioned to me they had this issue after installing the new windows update (1903) and since he had previously deleted the SW install file set for 2019 SP3 he had to re-download the file set then the first time it 're-installed' it worked fine afterwards.

If you already have the full file set try run a repair and if that fails I would see if anyone else has a solution, or just contact your VAR

So in the last 5 days both of my PC's have ended up with the BSOD thanks to the 1903 update. I had to completely reload both machines and now they are running fine. There must be something unique in my computers, because I know others have upgraded without issue.

At logon, the user see a Solidworks installation box pop up for SW 2018, the progress bar would move along, then start rolling back, a shortcut would appear on the desktop, then an error message relating to a fatal problem with the shortcut! This would immediately be followed by a SW 2019 box with exactly the same progress, rollback, shortcut creation and error.

This happens to all users (local admins and regular users) and despite the users not having SW set

to start automatically at login.

The same progress box appears when the users clicks a shortcut for either 2018 or 2019 in their start menu. But if they browse to C:\Program Files\SOLIDWORKS 2019\SOLIDWORKS\ and double-click on SLDWORKS.exe manually, Solidworks opens fine!

In Event Viewer, you get the following logs appear just after the user logs in.

After the 1903 update, we had various types of issues on different computers. When the subsequent updates stopped, I created a fresh Win10 installation USB drive and did a repair installation keeping the files and apps. So far, all computers have been running normally since doing the Win10 repair installations.

Scott Perman & Michael Yorke: Have either of you or your VARs been able to determine the root cause of the issue? Our scenario is very similar, except that it's Solidworks 2018 SP4 and the Windows 10 1809 upgrade that's triggering a repair/reinstall.

We have a VM set up in order to take snapshots, test, roll back, and reupgrade. Interestingly enough, we have it configured with side-by-side installs of 2018 SP4 and 2019 SP4, and only 2018 is affected. If you have anything you'd like us to try, let me know.

The main suggestions our VAR has had so far have been complete uninstallation and reinstallation, or to let the repair finish after upgrading to W10 1809. Both are infeasible, because we have 100+ clients with Solidworks (uninstalling and reinstalling would bring our engineering team to a halt), and end users do not have admin privileges so they cannot complete the repair themselves.

Hi, The VAR was no use in our case. They suggested re-installing, so we took that as an opportunity to just upgrade from 2019 SP2 to SP4. This solves the issue for us on the half dozen I have tried so far.

I don't have the time to troubleshoot the issue too much, but it was definately related to the upgrade of 1903 for us, so it's interesting to read your upgrade to 1809 caused it for you.

You mention you are already runinng 2019 SP4, so perhaps you could re-install/repair this version from the admin image. (how are you deploying Solidworks?) I appreciate this effecitvely an uninstall and re-install, except it might be quicker for your users to perform the repair. Test on your VM.

We've only installed 2019 SP4 on the VM as a test to see if it's also affected by the 1809 upgrade (which it isn't, fortunately, and runs just fine after the Windows upgrade). We do have an opening in the coming weeks where we plan to deploy 2019 SP4 (admin image via SCCM). It'll also be installed side-by-side with 2018 though, because existing in-flight projects will go to production and will finish up in Solidworks 2018, so the issue unfortunately can't be sidestepped by having everyone use 2019 instead.

One thing I did notice while testing yesterday was that the file count in the Solidworks 2018 folder on 1809 was different, specifically, the following were missing (via WinMerge):

\data\adobe\resource\cmap\AdobeFNT14.lst

\lang\toolboxapi.chm

\Toolbox\data utilities\sldsetdocprop.exe

\Toolbox\lang\ConfigureU.dll

\Toolbox\lang\grooveu.dll

\Toolbox\lang\hardwareu.dll

\Toolbox\lang\PowerTransu.dll

\Toolbox\lang\Steelu.dll

\Toolbox\lang\SwBrowser.dll

\Toolbox\lang\SwToolbox.dll

Copying the files over from a known good installation does not prevent the repair prompt, however. I'll have IT revert the VM back to 1803, and validate that the installation folder is complete prior to the 1809 upgrade. I may have them disable our anti-virus before the 1809 upgrade and see if that helps at all. Anyone else test this or is willing to share what AV they're running? We're on Sophos over here.