3 ms·

I have a non-computer-savvy friend who regularly has to reinstall nvidia graphic drivers because windows 10 update REGULARLY overwrites them with drivers that C

by jokoon 7y ago

I have a non-computer-savvy friend who regularly has to reinstall nvidia graphic drivers because windows 10 update REGULARLY overwrites them with drivers that CRASHES blizzard games (world of warcraft, overwatch). Has to be done every 4 days or something like that. It's really weird to not know who is at fault here, if it's nvidia, microsoft or blizzard. There are no good way (other than disabling updates) to prevent windows update from overwriting drivers. I wish microsoft would do something about this. Can't even remember if I submitted some feedback. Not to mention this computer is crazy slow since the upgrade from win8 to win10. I know the usual "get a SSD", but that computer was NOT THAT SLOW before the upgrade. Anyway this computer is a all-in-one, which has weird hardware. But still, it's a i7, with 6GB of ram. It's hard to believe it takes so long to open the start menu or just a folder. Oh yeah, other thing: another friend bought an used laptop which had some insider preview enabled. 3 weeks ago her microphone just stopped working. Apparently you cannot remove an insider win10 build WITHOUT REINSTALLING. I was not able to fix it. I'm not even a maintenance guy.

derefr 7y ago
> Apparently you cannot remove an insider win10 build WITHOUT REINSTALLING. Well, yeah. If a beta takes a wrong direction in the design of a new on-disk data structure, do you really expect them to write a reverse-migration that turns it back into the old format? That's a lot of work for a tiny point-release on branch of development they're not even sure they're going to make public. No commercial OS supports this.
- TeMPOraL 7y ago
  They could've warned instead of defaulting to failure. I wish they'd ease up with signing core system files with short-lived certs either; I once had to reinstall my PC after not booting into Windows for ~3 months - when I tried to start Windows after that break, I discovered some core DLLs had expired certificates, preventing the system from booting.
pvg 7y ago
Apparently you cannot remove an insider win10 build WITHOUT REINSTALLING. You can go to the previous install you had quite painlessly. It's in 'recovery options'. You don't need to set a restore point, it just works.

by jokoon 7y ago

derefr 7y ago

> Apparently you cannot remove an insider win10 build WITHOUT REINSTALLING. Well, yeah. If a beta takes a wrong direction in the design of a new on-disk data structure, do you really expect them to write a reverse-migration that turns it back into the old format? That's a lot of work for a tiny point-release on branch of development they're not even sure they're going to make public. No commercial OS supports this.

TeMPOraL 7y ago
They could've warned instead of defaulting to failure. I wish they'd ease up with signing core system files with short-lived certs either; I once had to reinstall my PC after not booting into Windows for ~3 months - when I tried to start Windows after that break, I discovered some core DLLs had expired certificates, preventing the system from booting.

pvg 7y ago

Apparently you cannot remove an insider win10 build WITHOUT REINSTALLING. You can go to the previous install you had quite painlessly. It's in 'recovery options'. You don't need to set a restore point, it just works.