PC Fails to Install Anything, Including Drivers, and Runs Extremely Slowly. Tech Mystery
PC Fails to Install Anything, Including Drivers, and Runs Extremely Slowly. Tech Mystery
I understand your perspective on doing things the cheapest way last. The main reason I hesitated to try it first was that if I end up locked out of windows again and can't install the software, my troubleshooting skills would take a hit. Now that I've formatted all drives, nothing remains on my Desktop. As a content creator and online business owner, having a broken PC means missing out on income, being unable to meet with my team, and disrupting operations—all of which are significant issues.
Thank you for the link! I actually had to search for it myself. It seems my PC stopped working:
https://imgur.com/a/J5eVYpp
I should mention I also tried an older 980 model—my TeamGroup mp44 m.2—but I didn’t install Windows on it because I didn’t want to risk losing important files. I plan to try the Rufus + ISO method and share the results, including any changes to the CPU.
Ah well that's pretty clear the cpu degraded already so your new one just run it on intel baseline settings since you've now updated the bios.
It might be possible to undervolt+underclock the ailing cpu but not sure of the precise method of that and since it's degraded already won't 'fix it' it'll continue to go downhill. Well you're getting the new cpu so point of messing with it?
I meant if you need to blat windows already and re-run setup might as well just try it with rufus+iso anyhow sometimes even if you can get windows repaired from the cmd prompt with Dism it can still have a problem I find 50/50 that winRE even works these days.
Every time I get access denied on rebuildbcd it's pretty much game over for that windows install only 2 times winRE helped was when I needed to edit some entries in the uefi and there were no other errors, when I was trying to install linux and it put the loader on the wrong drive.
Another time was when sptd2.sys got installed as part of some virtual drive/ramdisk program and turns out that is a 3rd party mess since the apps that uninstall it safely are history and if I simply disabled it on autoruns windows just collapsed, and even though sfc+dism fixed windows - said no corruption/ re-enabling the autorun with regedit from cmd prompt would not - windows wouldn't load so had to rinse/rinst. Dunno exactly why it hit a brick wall spdt2.sys just somehow embeds into the system and borks it nicely. So not using any virtual dvd/ramdisk 3rd party apps any more.
Sounds like you can get to windows so if you can just run dism from there with your fresh cpu - that's probly ok. But
clean install
is often recommended after cpu change anyhow.
Dunno how you manage your MS product key - do you have the thing written down or have you setup an MS account so you can just login with digital license? It is a must to keep a record of the credentials you used to set that up.
Run 'wmic path softwareLicensingService get OA3xOriginalProductKey' - from elevated cmd prompt . If you can make a note of your product key if you don't have the documentation to hand it could help.
I'd unhook your windows hello! login and switch back to pwd login too- before switching cpu. Changing the tpm can bork windows hello! since it's linked to the tpm, bios+cpu. Then you can get challenged for your credentials and how do you get a verification email if you're halted at login and can't access the desktop and email client? Then you'da needed to have setup a moby verification with sms beforehand. - or have a second device to receive emails to fetch the verification code.
Can workaround it if you have a 2nd local administrator a/c on your pc. which you would've needed to setup beforehand too - and reset the windows store with wsreset from the run dialogue. That puts your local pwd login back to your other main account so you can login with a pwd and get to the desktop and then sign in to ms ac from the start menu.
Thanks to all the people who jumped in to help me out!
it was more than helpful, It turns out it was the CPU as the culprit. Either from deteriorating or the microcode issue someone mentioned IDK, My guess would be on the former But regardless Things are fixed with the CPU replaced!
the thing that works always ends up the last thing.