- Joined
- May 14, 2002
- Posts
- 87,509
- Reaction score
- 38,764
Nothing worse than upgrading software and finding out your company is being used as a beta tester without knowing it. We upgraded from Solidworks 2013 to 2014 and it's been an abject failure. We upgraded the graphics drivers as recommended by Solid Works, did the upgrade, and then watched as one user after another had crashes and stability problems.
SW insists it's not their drivers it's our systems, worked with 2013, not with 2014 but it's not their fault. We've already replaced 2 systems, Dell won't change out the graphics cards(Nvidia boards seem to work, AMD's don't work well with new drivers and 14).
now we're seeing lots of secondary issues like monitors not working after a system goes into sleep mode. We get the Desktop Windows Manager has stopped working which will suddenly turn a monitor off, or the system will come out of sleep and now one monitor is black and you get that message. Sometimes you can restart the service, sometimes it's already started. It appears to be related to the Solidworks drivers although again they insist it's not their problem it's Dell or Windows.
What a pain in the neck.
I had one user who I suggested he update his BIOS, he did, but I forgot to warn him to suspend Bitlocker first and now every reboot it asks for the recovery key because of course the BIOS is different than it was when he encrypted it. My fault was focused on the Windows manager problem and forgot to warn him about Bitlocker.
SW insists it's not their drivers it's our systems, worked with 2013, not with 2014 but it's not their fault. We've already replaced 2 systems, Dell won't change out the graphics cards(Nvidia boards seem to work, AMD's don't work well with new drivers and 14).
now we're seeing lots of secondary issues like monitors not working after a system goes into sleep mode. We get the Desktop Windows Manager has stopped working which will suddenly turn a monitor off, or the system will come out of sleep and now one monitor is black and you get that message. Sometimes you can restart the service, sometimes it's already started. It appears to be related to the Solidworks drivers although again they insist it's not their problem it's Dell or Windows.
What a pain in the neck.
I had one user who I suggested he update his BIOS, he did, but I forgot to warn him to suspend Bitlocker first and now every reboot it asks for the recovery key because of course the BIOS is different than it was when he encrypted it. My fault was focused on the Windows manager problem and forgot to warn him about Bitlocker.