@Lopaka you didn’t rest you case, just that the conflict.that’s causing the symptom hasn’t been ID’d and fixed…
I had suggested you get or borrow a Microsoft Mouse, for testing. And Cat explained that you should completely uninstall the Logitech driver. But you didn’t. You instead got another Logitech mouse which probably uses the same driver that your previous mouse used.
I would tend to blame the Logitech mouse driver under Win10.
Have you asked about problems in the Logitech driver forums in regard to Windows 10 ?
You might also try installing 32-bit SketchUp, if it’s the 64-bit edition that you are having issues with, … or visa versa.
You should have a look at this document too, read and understand it…
http://forums.sketchup.com/faq
There might be an issue with SU, but so far this topic does not give Trimble anything to work on. Unless a problem can be tracked to a specific place in code via crash dumps or can be reproduced independently, the developers have no clue where to look. Also, the fact that it has been reported on only a couple of machines out of the millions running SketchUp argues strongly that there is something particular to those systems.
People here are trying to help. Insulting us won’t improve anything.
Have you tried safe mode and clean boot yet? I don’t have a link for Win 10 instuctions, but setting those boot states via msconfig is relative pleasant as you do it before before rebooting.
I don’t remember if you wrote that you tried the 32-bit installer as suggested above…
I have not tried the 32-bit version…
Was working with it today… Had minimal lockups… At one point, it seemed to lockup up every 10min… almost on the nose. The generic mouse seems fine.
I have no idea how to produce these logs that have been mentioned. I will research it and see what I can pull up.
Im still going to do a clean install of Windows. I was previously on Win 8 and got the free upgrade. What a sucker 
You have a big model. Do you have autosave turned on? Is the model on your local harddrive, on a network drive or a detachable drive? Autosave is known to make SU unresponsive with large models when it kicks in.
Anssi
1 Like
Yeah I am guessing you DID NOT get the ga zillion e-mails saying DO NOT UPGRADE to Win 10 . . Yes re install 8 and a lot of the problems will go away . . Don’t forget to save the files ( all of them Doc’s, Pic’s and down loads and the Sketchup files ) to a External USB Hard drive before doing any thing drastic . . Do not forget to Format before re installing the windows O/S
Files are saved on my laptop HDD.
Autosave is at the default of 5min intervals.
The issue persists even with autosave turned off.
Never received any email stating to not upgrade. Cant rollback as the Win10 has removed my default OS files. Thanks MS.
And yes, I know how to backup files and format drives 
As for my SU projects, each usually has about ~50 save files. I save to a new file/name any time that I make huge changes. I also save to the same file periodaclly. My SU project folders are very complete as I have seperate folders for everything I do.
I give up. Its still bugging out. I also noticed that when I have SU open, that my laptop is switching back and forth between the onboard GPU and the GTX. This could be a bug with Nvidia… The Nvidia drivers are current. It does not switch back and forth with any other program. So, in short, something is causing my mouse to bug and my GPU(s) to bug. This all started after the SU upgrade. Who is to blame remains to be seen. For all we know, it can be all three parties involved (MS, SU, Nvidia…) All I know is that im done. I can no longer deal with the lock ups. Ten years of fun… gone. Owell, it was fun while it lasted. Thank you all for the assistance. Take care.
check your battery save mode settings, it’s a common to flip-flop the graphics cards in save mode on many laptops…
john
Check in your Nvidia control panel 3D application settings that SketchUp is set to use the Nvidia. The Automatic selection might be doing this.
Anssi
It’s always a shame when a 77 replies long discussion returns no result…
2 Likes
Someone noted when SU is updated, the Nvidia 3D settings have to be reset on laptops or the graphics will flip-flop. Some programs retain the setting, but not SU. Though that maybe because each new version of SU is an independant install.
While the application still carries the name “Google SketchUp” in the Nvidia control panel! 
Anssi
Yea, but did you expect any different? When someone says 6 days ago “I’m outta here”, it usually means our wonderful community of users will hang in there above and beyond the call of duty to be nice to the person and help, and we’ll challenge the dreaded centi-thread beast once again.
Already checked the Nvidia settings. It was one of the first things I did. It remains set to the Nvidia card. It never chanhed will using SU 2015. Ive also set it to run on the onboard, and with same results (locking up)
Just checked battery settings. All seems to be fine and my battery is always fully charged (as I never run the laptop unplugged)
You wouldn’t by chance be using the Windows add-on called “KatMouse”. It affected my SU Make 2016. Turning off KatMouse makes everything OK.
Nope. Not using KatMouse.
UPDATE:
I started a new project. Ive been working with it for about an hour now… and ZERO lockups. Im still using SU 2016. At this point, I am thinking that the previous project was bugged due to the fact that I started it on SU 2015 and then continued progress on SU 2016. There lays the bug. Not sure what happened, but I did have some elements that were downloaded from 3D Wharehouse. I also had several large textures. I did remove the elements and textures, but continued to experience the bug. Im thinking that, although elements were removed, that the save files perhaps carried over their information to new save files. This is interesting. Furthermore, I had purged all unused textures. So, perhaps it was the texures. Perhaps it was an element that had bad script attached. Or, perhaps it was a plugin that had malicous code within (I only installed a few plugins this time around, opposed to a slew of them previously…)
What I suggest be done:
-
look into what happens when moving from 2015 to 2016.
-
all plugins should be reviewed by Trimble and/or the community to ensure there is no errorneous code within, since a virus scan will not pick up such code.
I will keep everyone updated on my progress. Lets hope that this issue is resolved.