F5F Stay Refreshed Hardware Desktop Temporary Windows profile due to removing the drive and linking to another machine?

Temporary Windows profile due to removing the drive and linking to another machine?

Temporary Windows profile due to removing the drive and linking to another machine?

T
tristangimp29
Member
55
11-02-2021, 07:23 PM
#1
Someone gave me two laptops. One ran Windows 10 with a spinning HDD, the other had Windows 11 and an NVMe drive. Both shared the same Microsoft account. The goal was to move personal files from the old to the new machine. I removed the old HDD and connected it via a USB to SATA adapter to the new one. I accessed the user folder on the old drive, but Windows insisted on adding permissions first. Then I used Robocopy to transfer files to the new drive. Afterward, I reinstalled the old HDD and powered up the laptop. During startup, Chkdsk began unexpectedly. I left it running while checking for updates, but no results appeared. Once Windows booted, a message appeared saying "Preparing Windows," then I was switched to a temporary user profile. It seems the Microsoft account on the old laptop had become corrupted. I attempted to fix it with SFC and DISM, but those tools didn’t help. Restarting in Safe mode let me access the account again, though the Start menu and other features still behaved oddly. During the transfer, multiple TEMP folders showed up in the old laptop’s Users folder, indicating a previous issue that had resolved itself temporarily. I also tried following a troubleshooting guide, but it didn’t resolve the problem. I’m curious—did using the same account on both devices cause the problem? I’ve transferred files this way before without issues, yet this time it failed.
T
tristangimp29
11-02-2021, 07:23 PM #1

Someone gave me two laptops. One ran Windows 10 with a spinning HDD, the other had Windows 11 and an NVMe drive. Both shared the same Microsoft account. The goal was to move personal files from the old to the new machine. I removed the old HDD and connected it via a USB to SATA adapter to the new one. I accessed the user folder on the old drive, but Windows insisted on adding permissions first. Then I used Robocopy to transfer files to the new drive. Afterward, I reinstalled the old HDD and powered up the laptop. During startup, Chkdsk began unexpectedly. I left it running while checking for updates, but no results appeared. Once Windows booted, a message appeared saying "Preparing Windows," then I was switched to a temporary user profile. It seems the Microsoft account on the old laptop had become corrupted. I attempted to fix it with SFC and DISM, but those tools didn’t help. Restarting in Safe mode let me access the account again, though the Start menu and other features still behaved oddly. During the transfer, multiple TEMP folders showed up in the old laptop’s Users folder, indicating a previous issue that had resolved itself temporarily. I also tried following a troubleshooting guide, but it didn’t resolve the problem. I’m curious—did using the same account on both devices cause the problem? I’ve transferred files this way before without issues, yet this time it failed.

C
CG_Snipey
Junior Member
42
11-04-2021, 01:34 AM
#2
The original profile remains available, retains admin rights, and the new account also holds admin privileges.
C
CG_Snipey
11-04-2021, 01:34 AM #2

The original profile remains available, retains admin rights, and the new account also holds admin privileges.

1
1234qaz12qaz
Posting Freak
773
11-04-2021, 03:23 AM
#3
It seems you've encountered repeated issues with the temperature profile after logging in. You mentioned restarting several times but still facing the same problem, and you also tried a troubleshooting guide without success. Let me know if you'd like further assistance!
1
1234qaz12qaz
11-04-2021, 03:23 AM #3

It seems you've encountered repeated issues with the temperature profile after logging in. You mentioned restarting several times but still facing the same problem, and you also tried a troubleshooting guide without success. Let me know if you'd like further assistance!

J
Jelly1233
Member
190
11-04-2021, 05:32 AM
#4
I’m not clear on your questions. I managed to log into the Microsoft account on the old laptop using Safe mode. I didn’t verify admin rights, but I pressed the Win key and R to execute CMD, which ran SFC and DISM as an administrator—so it seems the account still had admin privileges. The new laptop’s account had admin access.
J
Jelly1233
11-04-2021, 05:32 AM #4

I’m not clear on your questions. I managed to log into the Microsoft account on the old laptop using Safe mode. I didn’t verify admin rights, but I pressed the Win key and R to execute CMD, which ran SFC and DISM as an administrator—so it seems the account still had admin privileges. The new laptop’s account had admin access.

E
eagle_eye324
Junior Member
9
11-11-2021, 10:48 AM
#5
I didn't realize I triggered the issue with the old laptop's user profile, so I reached out in case something unexpected occurred. I attempted to recreate the situation using virtual machines on my home computer. I hoped this would help me identify and resolve the problem. In reality, the user profiles of my VMs were unaffected. It appears the profile was damaged on the old laptop's drive, not due to my actions.
E
eagle_eye324
11-11-2021, 10:48 AM #5

I didn't realize I triggered the issue with the old laptop's user profile, so I reached out in case something unexpected occurred. I attempted to recreate the situation using virtual machines on my home computer. I hoped this would help me identify and resolve the problem. In reality, the user profiles of my VMs were unaffected. It appears the profile was damaged on the old laptop's drive, not due to my actions.

H
HeatherHannah
Member
194
11-12-2021, 10:57 AM
#6
Ensure you can reach the previous login without using safe mode. Proceed by executing chkdsk and sfc -scannow via CMD to detect and resolve any disk issues.
H
HeatherHannah
11-12-2021, 10:57 AM #6

Ensure you can reach the previous login without using safe mode. Proceed by executing chkdsk and sfc -scannow via CMD to detect and resolve any disk issues.