F5F Stay Refreshed Hardware Desktop Several problems may arise after deep cleaning a PC.

Several problems may arise after deep cleaning a PC.

Several problems may arise after deep cleaning a PC.

Pages (2): Previous 1 2
P
plgamer1
Junior Member
26
07-26-2021, 03:41 PM
#11
For anyone encountering this problem later, possibly with similar concerns (HOW??), there’s little certainty about the exact steps needed. It remains unclear how the situation developed, but... well, it’s fine. The GPU issue seems resolved from a CMOS reset or switching between legacy and CSM in BIOS. The boot problem was more involved, yet if I had known what to look for earlier, it would have been much simpler. In the initial images, you’ll notice the C:\ partition is one, while others are divided into EFI, backup, and main partitions. This happened after formatting the drives during the Windows installation process, which created extra partitions needed for installation and recovery. It might have been a side effect of having multiple drives connected during setup, but it was directly caused by the way they were formatted via the installation media. Whether the EFI partition existed for C:\ or not is uncertain, especially since it was formatted identically to other drives through the same media—this often generates the required partitions (which I didn’t need on storage drives, but did on my boot drive). My approach was to reorganize files across the drives, remove the partitions entirely, and format them using Disk Manager > Simple Partition. However, I tried this second time when facing CMD command issues and ended up without any boot partitions. To recover the EFI partition on C:\, I followed a comment from another forum thread: https://forums. To add and set it up, I had to go through several steps: - Disable Fast Boot - Turn off Hibernation - Disable Page File - Turn off System Restore - Shrink the partition After shrinking, I used diskpart commands to adjust the partition size. If successful, but it risks failure—especially if you’re working on the main Windows install drive and have similar changes—check Event Viewer > Windows Logs for errors (red circle, yellow triangle labeled 'Defrag'). Look under "Diagnostic details" for the last unmovable object. Delete any suspicious files, then repeat the shrink command until it works. After that, continue with the remaining commands from the original post, except the final one after exiting. Then create the EFI partition, format it with FAT32, assign it a letter (e.g., H), and exit. Once done, run: bcdboot C:\Windows /s H: /f UEFI It initially worked but still displayed bootmanager as an odd volume 10. Use bcdedit to get the partition ID, then replace the old partition with a new one using bcdedit. After shrinking, restart and use powercfg.exe /hibernate on to enable fast boot and restore hibernate options without BIOS access. The reason or method behind this sequence remains unclear, possibly linked to installing NVMe during a broken Windows installation. Still, cleaning my computer feels like a daunting task now.
P
plgamer1
07-26-2021, 03:41 PM #11

For anyone encountering this problem later, possibly with similar concerns (HOW??), there’s little certainty about the exact steps needed. It remains unclear how the situation developed, but... well, it’s fine. The GPU issue seems resolved from a CMOS reset or switching between legacy and CSM in BIOS. The boot problem was more involved, yet if I had known what to look for earlier, it would have been much simpler. In the initial images, you’ll notice the C:\ partition is one, while others are divided into EFI, backup, and main partitions. This happened after formatting the drives during the Windows installation process, which created extra partitions needed for installation and recovery. It might have been a side effect of having multiple drives connected during setup, but it was directly caused by the way they were formatted via the installation media. Whether the EFI partition existed for C:\ or not is uncertain, especially since it was formatted identically to other drives through the same media—this often generates the required partitions (which I didn’t need on storage drives, but did on my boot drive). My approach was to reorganize files across the drives, remove the partitions entirely, and format them using Disk Manager > Simple Partition. However, I tried this second time when facing CMD command issues and ended up without any boot partitions. To recover the EFI partition on C:\, I followed a comment from another forum thread: https://forums. To add and set it up, I had to go through several steps: - Disable Fast Boot - Turn off Hibernation - Disable Page File - Turn off System Restore - Shrink the partition After shrinking, I used diskpart commands to adjust the partition size. If successful, but it risks failure—especially if you’re working on the main Windows install drive and have similar changes—check Event Viewer > Windows Logs for errors (red circle, yellow triangle labeled 'Defrag'). Look under "Diagnostic details" for the last unmovable object. Delete any suspicious files, then repeat the shrink command until it works. After that, continue with the remaining commands from the original post, except the final one after exiting. Then create the EFI partition, format it with FAT32, assign it a letter (e.g., H), and exit. Once done, run: bcdboot C:\Windows /s H: /f UEFI It initially worked but still displayed bootmanager as an odd volume 10. Use bcdedit to get the partition ID, then replace the old partition with a new one using bcdedit. After shrinking, restart and use powercfg.exe /hibernate on to enable fast boot and restore hibernate options without BIOS access. The reason or method behind this sequence remains unclear, possibly linked to installing NVMe during a broken Windows installation. Still, cleaning my computer feels like a daunting task now.

Pages (2): Previous 1 2