fix solidworks 2017 installation and crash

[jenuary]

Good morning to all,
I wanted to share a problem encountered these days and the solution.
after purchasing a new laptop, I installed solidworks 2017 from cd; as we know during the initial stage of installation
the program verifies any new service spack and proposed to me to download 4.1.
I chose to download the lighter package, i.e. only the difference files between sp.0 and 4.1 (1 gb) instead of the complete one of 12 gb.
the installation went well (at least it seemed), but then I realized that working, at the only click in one of the buttons of the macro bar
the program crashes immediately.
if you remember we deepened the same topic about a couple of years ago, the same thing happened in windows 7 when there was an update of windows kb3072630 that changed the bets in the vba register by crashing the program, then resolved by the 2016 version sp1 or uninstalling it before installing solidworks.
this time we are in windows 10.
the problem is that by downloading the soft version of the service pack 4.1 the installation is not perfect,
I recommend downloading the complete one from 12 gb and everything will go smooth (at least I hope).

I hope it can be useful for someone.

 

[MassiVonWeizen]

thanks for the information. put in the drawer of life saving things

 

[Atreiou]

personally when I check once a year sw, I make tabula rasa of the previous one and reinstall everything from scratch.
I understand that in many situations this is a little difficult to do. .

 

[re_solidworks]

2017 I installed it and removed it 2 times.... the first time a few months ago, I had to maintain also 2016, but in 2017 they changed something and when I opened a file with double click, for example to explore resources or from the pdm, with 2016 already opened a new session of 2017 and the file was opened with the latter. too dangerous, I risked to convert in 2017 files that had to stay in 2016.. .
last week I decided to take the ride, but it wasn't a good experience. we spent almost a day turning around malfunctions and eventually decided to restore the backup of the previous day and continue with 2016. to quote the worst three:
1- if there is a hidden envelope subaxis in a set, the lines in the table are generated incorrectly. I had edges in sight that they were represented as erroneously enveloped.
2-crash systematic in the generation of some edrawing files. I tried in every way and on multiple pcs but without success. the same file was generated quietly with 2016 and after the restoration of 2016 I tried successfully
3- this is the most serious. the functions of assembly are not reconstructed correctly, remains a reconstruction light that cannot be removed. I tried to remake the functions with 2017 and in some cases there is no way to remove them. It doesn't mean anything, it's not mistakes, but if you open a great together with these problems, reconstruction becomes secular.

I wonder if it's possible. . came out a year ago, we are at the service pack 4.1, I also tested the 3.0 with the same problems. This year I paid for maintenance for nothing and it certainly doesn't make me excited. We usually noticed problems within 2-3 days, but if in some hours we tribulated this way... I wonder what jumps out after a few days! As said we will jump 2017, we will go straight to 2018 if it will be stable enough to be used in the productive field. That doesn't make any sense anymore. 2015 was a disaster in stability, 2016 is good enough, we know the problems and we are accustomed to turning around, 2017 not even installed for excessive instability... if 2018 will still be so I think to stop at 2016 for 10 years and at least I stop spending money that equal the enrollment of a beta testing program! :
My dealer told me that there are companies that use it regularly... but my question arises spontaneously.
Aren't they edrawing? do they not use functions together? don't they use eavesdropping?
in our work we must be innovative and have cutting edge tools... but if being innovative means throwing your time to find shortcuts and employ more resources to achieve the problems of the instrument rather than focus on the project... Maybe it's better to be careful.

What do you think of this 2017?

 

[drake]

Thank you for sharing your experience, since I was thinking about moving to 2017. Still ds is peeing out of the pot! are also undecided if renewing assistance... I still have to think about it. I do not use the functions that you use, I hope someone else will also say his experience with 2017. However, I have said so many times here on the forum, each version has its "problems" also 2016 and x me these problems were not really trouble! 2016 does not update the properties of the separate cut, that is, you lose time to fill out the properties that go to read the size you want to bring back to the table with appropriate notes and then when you change the size this property is not updated! I noticed after delivering a job that was completely wrong (I noticed my clients... think that's a good figure I did). it seems that with 2017 it does not show up, but I have not checked sincerely. other problem I had with 2016 and that assistance confirmed me was also present with 2017 (I don't know until which sp) was the incorrect export in .sat or .iges format of multibody parts with hidden bodies. Hidden bodies were equally generated and so if you provided these files to someone who loaded them in autocad, he saw an incorrect pattern. look further news on these great new releases that to hear them just look at the monitor and the project is done!

 

[Atreiou]

My work consists of assembling commercial parts in the hydraulic-food sector, I do not make much modeling.
I just went to 2017 and for now I didn't find any strange problems, I would certainly like the assemblies to turn faster especially when I apply the couplings, but I admit that sometimes it could be the solids that suppliers send me and be a little too heavy.
My most frequent problems however are the virtual parts together, sometimes it can happen disappear without reason,
today there are and between 15 days there are no more, it often happens that you understand after windows updates, or at least the last time happened in that case.