Software Support > GroovyMAME
Windows 10 - worse performance?
smass:
--- Quote from: Mike A on October 10, 2018, 07:54:39 am ---What am I doing differently with updates? I must be an outlier because I never have any issues. All of my work and home computers are on auto-update. I honestly never have any problems.
--- End quote ---
Same here. Windows 10 on 8 different comps that I own. All working fine with auto updates. Not sure what the disconnect is....
schmerzkaufen:
Well I've mentioned the mumbo, again; it did not affect all machines and editions, or not all necessarily with the same heavy consequences.
If your computers aren't concerned, of course you've experienced no issues...
Calamity:
I think it's caused by incompatible drivers or hardware issues. In my case, I bought this laptop with 7 home preinstalled. It was a fast laptop, I remind compiling MAME in 15 minutes back then. It worked perfectly well with 7 for a few years until 10 was available. I didn't hesitate to jump into 10, but unfortunately the update process wasn't smooth at all, it failed the first and second attempts, then it worked maybe in the third. Each attempt took maybe 6 or 7 hours (seriously). Once installed, I instantly noticed that boot times were absurdly long. I thought it would be faster than 7 on that regard (8 was faster). I spent some time optimizing things and I finally got a more or less decent setup, but then suddendly the system started to freeze randomly. Next major update iterations have been equally terrible, needing several attempts each. The final one (1803) never succeeded after nearly 10 attempts. So I decided to replace the hard drive with a new SSD and try a fresh install of 1803. To my surprise it was installed and ready to use in a few minutes. No more freezing, everything working great again, for the first time since I upgraded from 7. So my understanding is that the first update from 7 to 10 made a mess with drivers and configurations inherited from 7, and this crap ball has been rolling since then getting bigger and bigger with each update. I am to blame for having trusted the automatic update feature when basic instinct warned me against that, after all it was installing an OS over an old one, what could go wrong? A fresh install is always a better idea. And this is my point: forcing full OS updates on people is a temerity.
smass:
Good points on the update thing. All my comps are fresh installs with one exception, a laptop that had windows 7 on it when I bought it and was updated to Windows 10 when the free window was open. I rarely us it, but when I do I have noticed its a lot slower than I remember when I first got it. I will try a fresh install of Windows 10 on it and see if thats the secret sauce :)
schmerzkaufen:
The install proces at least up to 1803 was flawed in that in order to install it made two things: a copy of the current version, and downloading the new version.
If you did not have enough space at some point (almost inevitable on the smaller eMMC/SSD), the install would fail and it would keep trying to download and install again, forgetting that it had already done these two steps.
To let the update complete itself I had to free as much space as possible (about 10~12GB which is practically the maximum free space you can have on a 32GB), cut off my internet connection during the reboot, then clear both the saved previous version (which I believe is kept a whole month), and the newer's install files which are stored in some folder and won't appear to the disk cleaner utility.
I also had to activate the metered connection to stop it from trying to redo the update again. Yes, because it was trying again, apparently unaware that it was already done.
Previously before all that I had tried to do the update from a thumb drive but it crashed, I also tried the utility that's supposed to let you move as many files as possible to another drive temporarily but it failed.
And even before that the 2017 fall update had similar issues but at the time Microsoft had let a dedicated update utility float around their website, it worked, but of course was removed before 1803.
Sure again when it works 10 isn't bad, but behind is the most incompetent service I have ever experienced from them.
To think their plan for the future is to turn their OS into a 'windows as a service' abomination...makes you wonder if they're hiring ex-EA employees to advise and work, or something.
In any case I'm keeping 7 and 8.1 as long as possible for what I absolutely need on Windows, and 10 will only ever be for non-precious and light stuff, as well as simply keeping up with the rest of the users. Hopefully the next Windows will not exclusively be the dreaded WaaS, and Microsoft seem to be working on a tick-tock production logic: crap, good, crap, good, crap, etc.