when starting solidworks 2018-2019 it crashes while initializing VBA engine.
I can't record this, because SW won't even start.
Anybody having the same problem or maybe even a solution?
Not much, beside uninstall and reinstall.
We are facing the same problem!
Solidworks 2019 even with SP01 does NOT support the latest Windows 10!
We already figured this out weeks ago with SP0 and rolling back windows to a later Windows 10 did the trick.
But now Microsoft decided to force the Windows 10 update to Win10 - 1809.
We installed a new PC with the latest Windows 10 and latest Solidworks but not working the same problem.
We tried different PC's and event Virtual Machines.
Try running command "winver" to show your current windows version if it is below 1809 SolidWorks should run.
But installing an older Windows version will result in forcing the update in a few days ....
@Solidworks Team don't you test the latest version of Windows with your software ?
We even tried to contact Solidworks but didn't get a reply!
Using the restore windows option we rolled back to an older version of windows and completely disabled windows updates.
Now SolidWorks is working again.
I on 1809 build 17763.253, both work desktop and my laptop.
2018 SP5 and 2019 SP1 running on both.
Desktop was on 1809 since it released.
We are unable to install it on a single VM or Laptop running 10 Pro 1809.
Okay, I will again give it a try with a clean windows installation, did you install special VBA or C++ version or just stock?
We only tested 2019 not 2018 ...
Thanks and best regards
It seems to be a region problem.
We have a combination of Language: English / Region: Austria or Germany.
Changing the region to USA seams to solve the problem ... but now we have invalid number formats (for us )
That, I have VS2017 community. Don't know if that make a different.
.Net 4.72 SDK, targeting pack
C++ Redistributable 2005-2017
I don't think VBA got any update. It's been dead for a few years.
Got it working!
Georg Hartmann : assuming by your name, you are also using an English installation on a system with German region settings.
Setting your regional format to English (United Kingdom) gives you the closest formats to our formats and a working SW-Instance
Yes also working for us!
what the actual **** ... working for me too
and yes I'm from germany
Glad you could help @Julian & @Felix
Good job. Worked for me!
wow! it really works! My previous setting is English(Netherlands) and now I set it to US, it works! These days I tried 2017, 2018, 2019 and wtf !
Thanks guys! Been using SW2019 without VBA for a month now... Finaly a solution that doesn't kill equations.
Thanks! I got the same problem. SolidWorks crashed while initializing VBA... SolidWorks 2019 SP3 or SP4, Windows 10 Pro and everything seemed in order with the graphic card. I changed the region from "Recommended - English (Sweden)" to "English United Kingdom" and it works!
does anybody know, if this issue is still present with SW2020?
We´re having the same issue with SW2019 on a VR with Win10 (1909), but changing language is not an Option (some old specialized Software won´t work)
But this issue only occours on a Virtual Machine. On all local Workstations, beeing installed in German, never had such issues?
On the VR, by initially starting SW, VBA module Fails and causes
- this error
- sometime SW crashes while starting
- sometimes SW starts, and you can work normally, but by closing it the standard way, it crashes.
BUT by starting any Office Application, VBA module seems to be loaded and running in Background.
Until that, SW starts without any Problem anymore within this session and until beeing rebooted.
I have the same problem in VM world using SW 2019 SP5 and Windows 10 v1803. Did you find a solution?
we had this problem on a CITRIX VDI environment. but not with exact error message as threat was started. see my comment from 2020-02-06
your IT guy found out, the problem was related to a temp folder in the user profile, solidworks would like to write to, but is not existing on a CITRIX VDI.
he changed the GPO (whatever this is ;-) for CITRIX profile. now it creates a TEMP folder in the user profile, each login, SW must have this tempfolder and cannot create if missing.
may this help you?
Thank you for the quick response Frank! My problem is also in Citrix VDI so I will look for this TEMP folder. If possible maybe your IT guy could share a screenshot of the GPO setting that corrected this.
i will ask him...
Retrieving data ...