-
Re: 2017 Start up times
Ian Worrall Jan 26, 2017 5:46 AM (in response to Steve Crompton)One of my colleagues had this problem. The fix was to remove the default file location under "Reference Documents" in the options screen.
-
Re: 2017 Start up times
Steve Crompton Jan 26, 2017 6:22 AM (in response to Ian Worrall)Thanks of the reply, but currently I dont have any folders being referenced in "Reference Documents"
Any more ideas?
Thanks
Steve
-
Re: 2017 Start up times
Ian Worrall Jan 26, 2017 6:26 AM (in response to Steve Crompton)No, sorry. I thought you had slow ASSEMBLY load times! *facepalm*
-
-
-
Re: 2017 Start up times
Glenn Schroeder Jan 26, 2017 8:14 AM (in response to Steve Crompton)Steve Crompton wrote:
How long is it taking for your seat of Solidworks to start up.
Just a few seconds.
-
Re: 2017 Start up times
Jeff Holliday Jan 26, 2017 8:17 AM (in response to Steve Crompton)Another discussion in this forum sounds like a similar situation. The problem was being caused by the antivirus program studying the SW file. Resetting their AV to not bother SW files supposedly solved the problem.
-
Re: 2017 Start up times
Steve Crompton Jan 26, 2017 8:43 AM (in response to Jeff Holliday)I saw that thread and stopped the AV looking at the solidworks files, unfortunately it made no difference.
Thanks
Steve
-
-
Re: 2017 Start up times
Rick Becker Jan 26, 2017 8:33 AM (in response to Steve Crompton)Best way to speed up load times is getting an SSD hard drive that the main program files are loaded from.
I assume you are launching SW from an icon and not loading a file at the same time.
-
Re: 2017 Start up times
Steve Crompton Jan 26, 2017 8:44 AM (in response to Rick Becker)Hi Yes
Launching from the icon.
Maybe a call to the VAR is in order.
Steve
-
Re: 2017 Start up times
Rick McDonald Jan 26, 2017 11:10 AM (in response to Steve Crompton)Are you running fully off your system or are you pulling files from you network?
I run completely off my desktop (no PDM either), my co-worker works primarily off the server files and his files are slow to load.
We do have all our support files on our desktops but if your company stores you support files on the server and the server is slow then your startup will slow down.
-
-
-
-
Re: 2017 Start up times
Deepak Gupta Jan 26, 2017 9:01 AM (in response to Steve Crompton)I see same behavior with SW2017.
-
Re: 2017 Start up times
Steve Crompton Jan 26, 2017 9:15 AM (in response to Deepak Gupta)Seems odd that some are getting load times of 20 seconds and we are getting 2 minutes. Surely it cant be a SSD thing can it?
I've put a call into my VAR. I'll let you know the outcome of that.
Steve
-
Re: 2017 Start up times
Deepak Gupta Jan 26, 2017 9:16 AM (in response to Steve Crompton)Could be as mine is not SSD.
-
Re: 2017 Start up times
Rick Becker Jan 26, 2017 9:26 AM (in response to Steve Crompton)I'm using Windows-7. I assume you are also.
Do a Windows search for msconfig and click on msconfig.exe.
click on the Startup tab.
Using great care not to turn off anything important, uncheck everything else. You will need a reboot when you exit.
Sometimes it is quite amazing how much is running at boot in the background.
-
Re: 2017 Start up times
Jeff Mowry Jan 26, 2017 11:06 AM (in response to Rick Becker)This is good for improving your computer's start up time, but shouldn't have any bearing on SW start up time once your computer is already started. Common culprits that bog down computer start up is anything Adobe, HP/Dell garbageware, and other peripheral items you don't really need to be pre-loaded into RAM before you're ready to use them.
I've seen similar behavior with SW start-up being slow in the past, and I run SSDs. However, sometimes SW is starting internal/external spinning drives on start up, and it appears to wait until those have spun up before allowing full start up. Annoying, since those drives are used as back-ups, not as anything necessary. Not sure where the setting for that is.
-
Re: 2017 Start up times
Rick Becker Jan 26, 2017 11:18 AM (in response to Jeff Mowry)Jeff Mowry wrote:
...but shouldn't have any bearing on SW start up time once your computer is already started.
Jeff I have found installed programs that scan/examine/autopsy each and every file that is accessed. This generally takes place without notifying the user it is happening and does have an effect on load of programs.
Jeff Mowry wrote:
Not sure where the setting for that is.
That's a feature...
-
-
-
-
-
Re: 2017 Start up times
Kevin Pymm Jan 26, 2017 9:24 AM (in response to Steve Crompton)Mine takes 13 seconds, including all add-ins.
-
Re: 2017 Start up times
David Mandl Jan 26, 2017 9:44 AM (in response to Steve Crompton)Primary things I would look at (this discussion's already hit on most of them):
- System RAM
- Hard Drive speed
- Processor speed (speed of a single core, not capacity of your 2/4/8/whatever cores together)
- Graphics card RAM allocation
- Add-ins
- Anti-Virus (is it trying to analyze the SW .exe?)
- What's your "idle" performance? (Go to Windows Task Manager, see how much CPU and RAM you're using with nothing open, maybe you're hosting some annoying services on your machine)
Chances are that in any random loading time problem, your biggest culprits are going to be HD and "idle" performance, maybe add-ins (which you said were all turned off). Graphics cards and system RAM aren't usually a big deal until you open files. I'll let more dedicated hardware nerds discuss where your processor comes into play here, but I doubt it's the primary suspect.
(I'd go into the details of my system, but for now I'll say that I'm in the 22-24s range for load times, and I mostly blame the "idle" processes. For some reason we have a service for helping run our phones that runs on each computer, and I hate it. It adds 8 seconds to my Outlook open times... which... why?)
-
Re: 2017 Start up times
Rick Becker Jan 26, 2017 9:35 AM (in response to David Mandl)David Mandl wrote:
... which... why?)
Phones are important for a business and the salesman for that phone system is gooooood...
-
Re: 2017 Start up times
David Mandl Jan 26, 2017 9:44 AM (in response to Rick Becker)Yeah, no kidding.
-
-
Re: 2017 Start up times
Glenn Schroeder Jan 26, 2017 9:59 AM (in response to David Mandl)We have a phone system connected to our desktops here also (Cisco Jabber), and I really like it. When someone is calling me a button appears at the lower right corner of my primary monitor that I can click. That will answer the phone and put it on speaker. There's another button I can click at any time to hang up. And when I need to make a call I can pull up the software and enter the number from my keypad. Hit Enter and it dials it. My phone is sitting on the far corner of my desk where I can barely reach it since I almost never actually need to.
-
Re: 2017 Start up times
Kelvin Lamport Jan 26, 2017 10:51 AM (in response to David Mandl)After full system reboot 9 seconds.
Subsequent new SW sessions 4 seconds.
SW17-SP1, SSD, No active add-ins,
-
Re: 2017 Start up times
I had this same issue with slow startup times. Do you have AVG Antivirus installed on your PC? If so... Uninstall AVG from your PC, Then Start SW 2017 again and see if it fixes your issue. If it does, you can then reinstall AVG and it will work just fine.
Hope This helps. It worked for me.
-
Re: 2017 Start up times
Steve Crompton Jan 26, 2017 10:27 AM (in response to Eric )Just come off the phone to my VAR. There is an SPR out just for this very thing.
Tried switching AVG and various services off but to no avail. So those of us that have this issue will just have to sit it out until Solidworks come up with a fix.
Thanks
Steve
-
Re: 2017 Start up times
Kelvin Lamport Jan 26, 2017 10:43 AM (in response to Steve Crompton)Please post the SPR number here, so that others having the same problem can add their vote to promote the fix.
-
Re: 2017 Start up times
Steve Crompton Jan 26, 2017 11:05 AM (in response to Kelvin Lamport)I've requested the SPR number from my VAR so I can post it here.
Steve
-
Re: 2017 Start up times
Deepak Gupta Jan 26, 2017 11:06 AM (in response to Steve Crompton)SPR #: 990482
-
-
Re: 2017 Start up times
Steve Crompton Jan 26, 2017 11:54 AM (in response to Kelvin Lamport)SPR990482
Opening Solidworks 2017 splash screen 'Loading Registry' for a few minutes (slow start-up
-
-
Re: 2017 Start up times
Kevin Pymm Jan 26, 2017 10:43 AM (in response to Steve Crompton)Have you tried uninstalling AVG as Eric suggested rather than just turning off the services? I'm sure there were still parts of AVG hanging onto SolidWorks somewhere & causing issues. Best to remove it from the equation totally, try running SW's & then reinstall. Worth a go if it sorted Eric's issues.
-
Re: 2017 Start up times
Steve Crompton Jan 26, 2017 11:06 AM (in response to Kevin Pymm)Unfortunately that's something that I will not be able to do. Company policy and all that.
My VAR did say that a lot of people had voted on it and marked its impact as high. So it would seem its a common issue with some.
Steve
-
Re: 2017 Start up times
Jeff Mowry Jan 26, 2017 11:09 AM (in response to Kevin Pymm)I've seen AVG lock down computers when removable media is installed (CD/DVD/thumb-drive) until the entire contents have been scanned. Wouldn't be surprised if such a thing is happening between AVG and SW. (This is one reason I prefer Avast.)
-
-
-
-
Re: 2017 Start up times
Glenn Schroeder Jan 26, 2017 2:41 PM (in response to Steve Crompton)I just re-booted and checked. 14 seconds from when I clicked the icon at the bottom of my screen until SW was loaded and ready to go.
-
Re: 2017 Start up times
Anna Wood Jan 26, 2017 3:56 PM (in response to Steve Crompton)My guess would be SolidWorks is hunting for a network path that is no longer available. Has anything been moved, re-pathed or re-mapped in your engineering environment?
-
Re: 2017 Start up times
Steve Crompton Jan 27, 2017 4:05 AM (in response to Anna Wood)Nothing has changed since we changed from 2016 other than the load times. Like I've said its a known issue and is apparently affecting many users. I think trying to track down the problem would take forever. My VAR told me that normally Solidworks give the VAR's a work round for certain problems, but for this one there is no known work around according to Solidworks.
They simply need to fix it asap.
Thanks
Steve
-
Re: 2017 Start up times
Its too bad you cant uninstall AVG. That's what SolidWorks Corp had me do, and I'm currently running with no problems. 8 Sec start up time.
-
-
-
Re: 2017 Start up times
S. Casale Jan 27, 2017 11:33 AM (in response to Steve Crompton)Oh snap, I'm average.
14.22 seconds with pdm client and routing add-in selected.
-
Re: 2017 Start up times
I am having this same issue.
The splash screen sits on loading registry for 1:25, then completes loading SW at 1:35.
We have three other seats that don't have the issue. They are all running windows 7. My machine is the only one running Windows 10.
We do not use AVG we use Kaseya Anitvirus.
The other odd thing is that when I installed SW it did not associate any of the file types to SW. I had to manually edit my registry to get the associates to work.
-
Re: 2017 Start up times
Rick McDonald Jan 27, 2017 6:20 PM (in response to Clint C. )It might be trying to find other files that were also not correctly associated.
check in the options / file locations and see that in all instances the paths that are listed to to use are valid paths and have valid files in them.
It may be timing out after not finding a path or file.
Another thing that might help is doing the indexing in Windows so that it doesn't spend as much time searching for files in directories.
-
-
Re: 2017 Start up times
David Puterbaugh Apr 3, 2017 10:00 AM (in response to Steve Crompton)Uninstall AVG. Reinstalled Solidworks. Problem gone.
AVG cloudcare is new for us. never had a problen with AVG until now.