F5F Stay Refreshed Software Operating Systems Windows 10 frozen in "Windows To Go" state

Windows 10 frozen in "Windows To Go" state

Windows 10 frozen in "Windows To Go" state

P
Petterine
Member
Find
60
07-06-2016, 09:57 PM
#1
I don't understand why this occurred, but my Windows installation identified itself as "Windows To Go." It seems this might have happened during the cloning process because of faulty SATA cables (I assumed all disks were failing). One disk appeared to be deteriorating, so I made a clone to another drive. After some time, I noticed it became unresponsive—data transfer stopped intermittently. I tried another clone, but without time to fix the case, I simply connected the new drive via USB and moved it inside. Over time, I experienced BSODs and occasional crashes, prompting Windows To Go to warn me to keep the USB plugged in to prevent data loss. Recently, I switched to a Western Digital Black SN750, which boots more slowly than my laptop's SATA SSD from six years ago. It could be that the installation was set to a Windows To Go configuration or mode. Even if this isn't the root cause, I'd prefer it not to be. Any suggestions on resolving this without a full reinstall? Thanks in advance!
Reply
Reply
P
Petterine
07-06-2016, 09:57 PM #1

I don't understand why this occurred, but my Windows installation identified itself as "Windows To Go." It seems this might have happened during the cloning process because of faulty SATA cables (I assumed all disks were failing). One disk appeared to be deteriorating, so I made a clone to another drive. After some time, I noticed it became unresponsive—data transfer stopped intermittently. I tried another clone, but without time to fix the case, I simply connected the new drive via USB and moved it inside. Over time, I experienced BSODs and occasional crashes, prompting Windows To Go to warn me to keep the USB plugged in to prevent data loss. Recently, I switched to a Western Digital Black SN750, which boots more slowly than my laptop's SATA SSD from six years ago. It could be that the installation was set to a Windows To Go configuration or mode. Even if this isn't the root cause, I'd prefer it not to be. Any suggestions on resolving this without a full reinstall? Thanks in advance!

Reply
Reply