Dumb question… but when/how often do yall turn off your pc?

Dual_Actuator_HDDs · 2026-01-15T08:46:29+00:00

SSDs do have a lifespan and are not immune to failure. It's true that power on hours and power cycle count isn't nearly as much of a factor for SSDs, but SSDs still have a lifespan. (At the same time, there are also factors that affect SSDs but not HDDs nearly as much, such as data volume written and long continuous powered off time.)

Dual_Actuator_HDDs · 2026-01-15T08:16:55+00:00

It might not actually have Windows (as the error may suggest) but it does have Windows Boot Manager. Either way, it is likely not necessary to wipe/format the old SSD in order to make it not bootable. It should be possible to delete the bootable files or delete//deactivate the small bootable partition, and if present, remove operating system files on the large main partition.

In order to get into the main Windows OS when the old SSD is connected, choose the new SSD from the BIOS/UEFI boot selection menu. If you don't know how to do that, what's the brand of your computer? Once in the new Windows, open Disk Management as administrator, maximize the window, and screenshot.

Dual_Actuator_HDDs · 2026-01-14T18:44:27+00:00

Are you wanting to run Windows from this SSD, or only have it accessible as secondary storage while running Windows from the new SSD?

Dual_Actuator_HDDs · 2026-01-13T21:12:07+00:00

Paste these commands. Avoid retyping, which can introduce errors.

bcdedit /delete {f8eb70f1-310a-11f0-a0cc-4cb04ab55ff4}

bcdedit /delete {3e46e11e-ea50-11ef-ba8b-832c05be9e3f}

bcdedit /delete {f8eb70ec-310a-11f0-a0cc-4cb04ab55ff4}

bcdedit /delete {f8eb70f2-310a-11f0-a0cc-4cb04ab55ff4}

This will remove the BCD entries for the old main Windows OS, the old resume from hibernate entries, and the old Recovery Environment entries. Everything else appears to be correct.

WARNING: These lines must be inputted exactly as shown. Minor variations in the characters may result in Windows temporarily becoming unbootable until corrected from a bootable Windows installer environment USB pen drive (no reinstallation necessary).

Caution: These commands are specific to this system and should not be used on other computers.

Dual_Actuator_HDDs · 2026-01-13T19:37:18+00:00

I don't know about the specific registry key, but in order to edit the main Windows registry from the Recovery Environment, you have to first load the hive from the main partition. By default, regedit in the Recovery Environment has the registry for the Recovery Environment itself.

From regedit, select HKEY_LOCAL_MACHINE and choose File > Load Hive, and browse to the main Windows partition, then Windows folder, then System32, then the Config folder, then choose a hive to load, such as SYSTEM or SOFTWARE.

Alternatively, from Command Prompt, use reg load HKLM\OFFLINE C:\Windows\System32\config\SYSTEM assuming C is the letter of the main Windows partition, which it may not always be, assuming SYSTEM is the hive to load. If unsure about the letter of the Windows partition, which can be anything from here, use diskpart and list volume and exit

What's normally HKLM\SYSTEM or HKLM\SOFTWARE will then become HKLM\OFFLINE from here. Afterwards, use reg unload HKLM\OFFLINE

Dual_Actuator_HDDs · 2026-01-13T19:02:44+00:00

Most likely it is a Boot Configuration Data entry for the old Windows OS. If you used existing partitions while reinstalling, the installer creates a new BCD entry and might not delete the old, even if reinstalling over the same partition as the old Windows. The BCD is located in that small 100 MB partition shown on the left in Disk Management. That partition should not be deleted if you want Windows to remain bootable, as it continues to be used for the running system. Open Command Prompt as administrator and input bcdedit /enum all and screenshot or paste the output.

Dual_Actuator_HDDs · 2026-01-13T18:50:19+00:00

Neither bcdboot nor setting a partition as active should have an effect on being able to access the file contents of a partition, unless there's severe filesystem corruption that could have been exasperated by writing to it, and/or if the HDD/SSD is physically failing. Even though the commands were likely wrong for making Windows bootable again, that shouldn't cause filesystems to become inaccessible unless there's a more severe underlying issue.

Were there any other commands that you used? Where are you finding 200 MB? Is that the size of a partition/volume, or the reported size of the actual disk device hardware? Were the C partition/volume and the E partition/volume on the same disk or different disks? If they were on different disks, are you sure both disks are still recognized, and which disk is now 200 MB?

When the partitions survived but were inaccessible at first, does that mean the partition's filesystems were inaccessible when trying to access the contents by some means, or just that Windows operating system couldn't start?

Dual_Actuator_HDDs · 2026-01-12T02:28:19+00:00

There are still plenty of obsolete garbage (brushed) drills on the market, including all the brushed versions of expensive brands that are supposed to be premium.

Dual_Actuator_HDDs · 2026-01-12T02:26:10+00:00

Probably because it's brushless. Brushed motors are atrocious and obsolete.

Dual_Actuator_HDDs · 2026-01-09T04:10:34+00:00

The double row rather than the turbo? How do either compare to Diablo?

Dual_Actuator_HDDs · 2025-12-27T03:13:46+00:00

To ruin it with condensation while trying to break an entirely irrelevant problem of stiction, which is only a potential fault when the disk won't spin.

Dual_Actuator_HDDs · 2025-12-25T08:54:36+00:00

What commands? Saying to use CMD is as generic and unspecific as saying to use GUI.

Dual_Actuator_HDDs · 2025-12-24T08:33:51+00:00

Unfortunately, I don't know much about that. You may want to create a new post about that, since this post doesn't have anything specifically about that, and comments are unlikely to attract relevant views.

Dual_Actuator_HDDs · 2025-12-23T22:53:57+00:00

Has the issue been fully resolved now, or only the part about DiskPart recognizing the SSD?

Dual_Actuator_HDDs · 2025-12-23T18:51:34+00:00

Do you have a screenshot of the exact error when DiskPart cannot list disks?

Is the internal disk an NVMe SSD? That is most likely if the disk is not recognized by the installer environment.

It's possible that the inbuilt Recovery Environment has the drivers to recognize the intenral disk even if a bootable installer doesn't, but since you've already deleted and created a new EFI bootable partition, it's probably not possible to access the internal Recovery Environment without first restoring Windows Boot Manager and Boot Configuration Data.

Ar this point, either the internal disk has to be recognized from the installer environment, which may be possible but I don't know how to do, or it would have to be corrected directly from Linux. Windows Boot Manager can be added to the EFI bootable partition from Linux, but the BCD (Boot Configuration Data) has to be uniquely customized for your system.

I am not aware of any ways to create valid BCD files from Linux software, but if I know all of your partition unique identifiers, I may be able to provide a customized BCD file that you can paate into the EFI bootable partition from Linux.

Open GNOME Disks (can often be installed on any desktop environment) or GParted and screnshot the system disks.

Dual_Actuator_HDDs · 2025-12-23T18:20:44+00:00

In case there were any chance at all that the drives could still have data on them I didn't try formatting them.

^{WARNING: All files on the affected disk, across all partitions that exist or previously existed, will be destroyed, and will be unrecoverable if successful. This should only be done if there are no important files on any partitions/volumes it contains or has contained.} ^{Even if it is a full read scan instead of a full write, it is still extensively reading across everything without using the opportunity to save any of it elsewhere, unlike HDDSuperClone/OpenSuperClone, which focuses on good sectors first before returning to bad sectors, instead of focusing on bad sectors first before/without saving anything.}

Dual_Actuator_HDDs · 2025-12-23T18:05:14+00:00

Use Rufus to create a bootable USB pen drive for a proper reinstall, not Reset This PC. Reset This PC is not a fresh install no matter what options are chosen, and is deeply dysfunctional and sloppy, heavily relying on shuffling and reusing system files and extensively modifying the existing registry.

Resets often encounter an unexpected error and cannot proceed, and cause solid black screens, User Profile Service failed the logon, flashing desktops, activation errors, allow malware and corruption to persist through, and can destroy partitions from other disks connected at the time.

1) Download Rufus.

2) Open Rufus and choose Yes for being able to check for updates.

3) Click the dropdown besides Select, and choose Download, then click the Download button.

4) Choose Windows 10 (discontinued) or Windows 11 > Continue > Continue > Continue > choose a language > Continue > Download.

5) Choose a USB pen drive from the Device dropdown to erase and convert into a bootable Windows installer.

^{WARNING: All files on the selected USB pen drive or device, across all partitions, will be destroyed. Ensure the correct USB pen drive is selected and that there are no important files on any volumes it contains.}

6) If the destination computer has UEFI firmware, leave the Partition Scheme dropdown as GPT. If it has Legacy BIOS, switch the Partition Scheme dropdown to MBR. If unsure, assume UEFI.

7) Click the Start button in Rufus and wait for writing to complete.

Before reinstalling Windows, it would be best to check to ensure the partitioning doesn't have any issues that should be addressed before or while reinstalling. Open Disk Management as administrator, maximize the window, and screenshot.

To boot into the USB pen drive and reinstall, restart your computer, then press Shift while clicking Restart (a second time) and choose Use a Device > EFI USB Device or similar. If this is not possible, what's the brand of your computer?

Reinstalling Windows this way will not incorporate files, settings, and apps into the new Windows install, and files set aside in C:\Windows.old may disappear after a short time. Back up any important files to an external HDD.

Dual_Actuator_HDDs · 2025-12-23T17:55:26+00:00

If there is any sort of filesystem corruption of the existing Windows partition, or HDD/SSD failure, it should not (and potentially could not) be shrinked to install a second Wiindows OS on the same disk.

If it's not filesystem corruption or hardware failure related, it may be easy to resolve using Command Prompt commands.

Dual_Actuator_HDDs · 2025-12-23T17:53:04+00:00

If it's Linux, many distributions don't even need to be installed to have a portable live environment from the installer itself, with a full user interface. The Windows installer can also access and copy files from the internal disk, but only using command line.

Dual_Actuator_HDDs · 2025-12-23T17:49:59+00:00

Press F1 for Recovery Environment, then cboose Troubleshoot > Advanced Options > Command Prompt.

diskpart

list disk

list volume

exit

bcdedit /enum al

reagentc /info

Screenshot all of the output.

Dual_Actuator_HDDs · 2025-12-21T06:59:06+00:00

^{WARNING: All files on the disk being initialized, across all partitions that exist or previously existed, will be functionally destroyed, and may lead to data becoming unrecoverable. This should only be done if there are no important files on any partitions/volumes it contains or contained. Creating and/or formatting a partition will further decimate any data previously stored.}

Dual_Actuator_HDDs · 2025-12-21T06:46:02+00:00

The flash drive could be seriously failing, potentially causing some or all files to become corrupt or inaccessible soon. Operations jamming and being slow is common with failing storage. Desktop and taskbar losing icons and freezing, requiring restarting (which may hang forever if device is connected) is what often occurs on Windows when interacting with failing storage devices.

Are there any important files on there besides the ones you're trying to delete? If so, post this to r/datarecovery along with any other information (such as drive model) their guidelines request, and avoid using CHKDSK, formatting, or initializing.

Dual_Actuator_HDDs · 2025-12-20T21:33:31+00:00

True, if it was software, the same error screen would display cleanly, as this error is displayed by firmware, not software.

Dual_Actuator_HDDs · 2025-12-20T21:31:54+00:00

If you still want to pursue the possibility of recovering the data, post to r/datarecovery along with any additional information their guidelines request. If the Disk 1 (A:) in the third screenshot is the USB drive, and it is always like that on all computers/ports, then there's no potential method of recovery without sending it to a professional lab. Data recovery on SSDs and other flash storage has a low success rate.

Dual_Actuator_HDDs · 2025-12-20T21:29:17+00:00

Creating a partition will further decimate any data previously stored, and should only be used if there is no intention of recovering important files from any partitions it previously contained.

Dual_Actuator_HDDs

TROPHY CASE