I_Swear_768p_Is_Enough

It seems that your Recovery Image has been corrupted. If you've recently been able to update to 2004, you should be able to connect to the Internet and use Reset This PC coupled with the Cloud Install option. This will download a new ISO of Windows 10 instead of searching for the compressed, and now corrupted, Recovery Image. If you've been unable to update to 2004, or just don't want to for stability reasons, you'll have to create a new system image. If you have a DVD-ROM drive, you can burn a disc, but I'd recommend just using a USB drive for this. Go to Microsoft's website and search for the free W10 ISO, put it on the USB drive, and boot with that drive. You can either do this through the boot priority options in the BIOS or through Advanced Startup in Windows. After that, all you might need to do is enter your product key. Sometimes this won't even be needed. If it requests it, you should check with any materials that came with your PC when you bought it or on the disc if you built it or otherwise installed Windows yourself. If your MS account was linked to your PC for a digital license (if you even have an account), you may be able to just sign in to accomplish this as well. Just in case you can't find it, here's the link on the MS Support site: https://support.microsoft.com/en-us/help/15088/windows-10-create-installation-media Best of luck!

It's been a day and a half of weird PC issues in my general circle of acquaintances, and I haven't experienced something like this before. This afternoon, I was asked to reinstall Windows 10 Home on one of my friend's PCs. He takes good care of his machines and likes to reformat them every once in a while for performance reasons (even though he's never seen any real benefit, but hey, his choice), but had been away from his rig when he wanted to do his yearly reformat of the OS. Since he primarily uses cloud-based storage solutions, he just told me to use the Reset This PC feature in the Settings App and that he'd worry about linking his MS account or otherwise importing his files later. I've used Reset This PC numerous times across many different machines, whether it be due to system instability on my personal rig following two awful W10 updates that couldn't be rolled back successfully or because family members have done something stupid with their machines that could only be solved with a fresh install of Windows. The PC in question has a Samsung EVO SATA SSD as the sole drive, and we know this thing has been a trooper and is in good working order. I booted into Windows, opened Settings, and used Reset This PC to clean the drive fully. I used the local recovery partition option since neither of us have touched the Cloud reinstallation from 2004 yet and didn't want to try a feature we've never driven before. The process started like normal, and reboot into the normal environment. Besides being stuck at 19% for what felt like hours, it proceeded at its normal sluggish pace until it reached 100%. However, instead of normally rebooting into the blue "Please Wait, Installing Windows" screen, it instead booted to the "Scanning C:" and "Repairing C:" screen as if the machine had been shut down incorrectly. This happened about 2 or 3 times from what I saw, but I had been doing work around the house at the time while keeping an eye on it, so it might have done this another time without me realizing. From what I witnessed, it pretty much scanned and repaired from 1% to 100% in a few seconds, and then would boot right back into "Scanning/Repairing." After the final time, it booted correctly into the OS installation screen, and took me to the setup page afterwards. My main question is, should this concern us at all? I'm really curious as to why something like that would happen, because whatever sliver of Windows 10 was there, it seemed insistent on fixing some sort of issue. We've had one bad Windows 10 install over, I'd say, 40 fresh installs between us on many different machines, but that one bad install really screwed us (so unstable, frankly it could've damaged hardware it seemed). I physically investigated the drive, it's recognized in the BIOS and seems to be mounted in the chassis and connected to the Mobo properly. Should I try to reinstall Windows again to be sure of a stable platform?

Just wanted to preface, I've never used the forum before as a poster, so if leave out pertinent information, just let me know. Sorry in advance! Yesterday, I had a really strange issue with my PC that I'm assuming was PSU related, but honestly it worries me on many levels. I just bought an Oculus Rift and was trying to find the ideal setup in my bedroom. I had set up everything thinking it was in a great spot, but it turns out that I needed to change rooms for practicality reasons regarding roomscale. I unplugged everything from my PC, flipped the PSU switch to off, and unplugged any other cables tethering my PC to the outlet and moved it to my other one. When I replugged in everything pertinent (PSU cable, Monitor power and DP, and KB/M) and switched the PSU switch to on, it double-posted normally and booted off my SSD into Windows 10. However, my Mobo has onboard WiFi and Bluetooth (I know, I know, but it's actually super relevant to my setup in my home due to the many other users sucking up Ethernet ports) and both just wouldn't work. Device Manager in Windows said that my WiFi drivers weren't working properly, so I tried disable/enable, reinstalling the drivers off the disk, and checking the UEFI BIOS. Everything seemed like it should work flawlessly, but it just didn't. I had no way of connecting to the Internet besides running a massive cable downstairs, and after doing that and installing drivers that way, it still just wouldn't budge. I decided to check to see if anything was dislodged in the case, so switched off my PSU and opened the side panel, where I found everything to be fine. Switching it back on didn't yield any new results. I had to go to work, so I decided to tackle the problem the next morning. When I woke up this morning, I decided to once more check the inside of the chassis to see if I maybe missed something. Turned the PSU off, opened the side panel, and again, everything seemed fine. Didn't even touch anything this time. But when I booted back into Windows after turning the PSU back on, this time the onboard Wifi and Bluetooth worked! I really have no clue if this is a sign that my cables are bad, if my PSU is dying, or if my Mobo is starting to show signs of wear and tear. Money's hasn't been exactly flowing recently with everything going on globally, so I really hope this is either cable or PSU related if anything other than a weird mishap, because replacing a Mobo would be pretty time consuming and more expensive than I need to think about right now. Thoughts? Specs that are pertinent: EVGA 650w 80+ Gold Modular PSU (az: https://www.amazon.com/EVGA-Modular-Warranty-Supply-210-GQ-0650-V1/dp/B017HA3SQ8) ASUS TUF Z390-PLUS GAMING (web: https://www.asus.com/Motherboards/TUF-Z370-PLUS-GAMING/)