Windows 10: All hell breaks loose after connecting drive to a different PC

I was helping someone migrate from one computer to another. Because there was a lot of data and time was limited I pulled the hard drive from the old computer and hooked it up with a USB adapter to the new one. To copy the data I used Windows Explorer on the new computer and navigated to F:\Users\Mike. When I clicked the folder to open I had to click a button to grant me access to the folder.

After a while I could browse and copy everything I needed from F:\Users\Mike.

I put the drive back in its old system and it booted up fine and everything looked normal. But, a few hours after I left all hell broke loose. First Windows blanked the screen and displayed a message at the bottom saying "Repairing disk errors. This might take over an hour to complete." with a little spinning dots icon above it. Then after a restart (or two) lots of other errors came up.

Dropbox error: "Couldn't start Dropbox. This is usually because of a permissions error. Storing your home folder on a network share can also cause an error"

Desktop: "You don't currently have permission to access this folder. Click Continue to permanently get access to this folder." (The user clicked Continue)

Acrobat Distiller: "Unable to create the temporary folder. Error -5 - Access is denied."

The background / wallpaper image is gone, desktop is black.

Windows Start Menu icon visible but doesn't respond to clicks.

There's lots of other little glitches. Earlier today I couldn't get to a command prompt from the Task Manager, but now I can so I'm running "sfc /scannow" to see if any of that helps.

I also tried reassigning permissions but ran into some errors there too.

And I tried logging in as a different user, but can't seem to accomplish that either.

I've removed drives to load data onto other computers many times in the past. Usually they're disposing of the old PC and not too worried about making it work again. But, as I recall I've been able to boot and run the drive in it's old PC with no real issues. Maybe it's something about Windows 10 that is different or maybe it's something else.

Thanks for any guidance!

:)

 

This windows 10 system has slowed my computer down, and is doing a lot of other weird stuff. I miss 7. At least it worked.

I am having the same problem. Some times al hell breaks loose. The keyboard will not work. It will not respond while typing.

 

N82 PC Suite new hardware issue

after getting pc suite to work fine and getting a good connection to my phone, I decided to download the map software.

All hell broke loose and now my PC does not recognize my telephone, or at least states that there are hardware problems. I have reloaded PC suite and software updater will not load due to "network failure". On another PC the phone is recognized (but the OS
is too old to load PC suite).

Any ideas fellow Nokia users?

 

What steps did you take prior to disconnected the hard drive from the USB port?

 

Just the regular "Safely remove..." command and waited for the green light to disconnect.

 

Not sure what happened then...normally something like that is caused by improper removal of the drive. Sounds like a clean install of Windows will be required. What I do in a situation like that is use something like Kyhi's recovery tools and a partition wizard program included on it to shrink the current OS partition to as small as possible and move it to very end of the drive, delete all other partitions and then do a clean install to the unallocated space at the front of the disk. After everything is retrieved from the old partition that needs to be, it can be deleted and that space reclaimed by expanding the existing partition or creating a new one.

 

Are there any permission fix tricks that might revive this machine?

 

You could try secedit - it is still supposed to work in Windows 10 (according to this MS blog) but I've not tried it.

To reset permissions to default run this in elevated command prompt Code: secedit /configure /cfg %windir%\inf\defltbase.inf /db defltbase.sdb /verbose[/quote] Source

I'd probably clean install myself but giving secedit a go certainly isn't likely to make it any worse than it already is.

 

Thanks for the idea. I just tried it then rebooted. Doesn't seemed to have helped.

I'm going to try adding a new user account then migrate the data over.

 

Added new profile from command prompt. Rebooted and the new user profile worked nicely. Then I used ForensIT profile wizard to copy the profile from the old to the new. After another reboot it signed in then took about 8 hours to get through "Updating Store App 1 of 81" When it finished the new profile had all the problems of the old one *Sad

 

Why did you do that (my bold here)? Do you think ForestIT caused the problem or updating the apps?

If a new profile works you could just dump all your documents into C:\Users\Public\Documents from the old profile and then copy them out of there into the new profile. Going through Public gets rid of authority issues (assuming everything else is OK).

Could be the permissions on WindowsApps are screwed though (if updating the Apps causes the issue) in which case clean install will almost certainly be quicker than trying to figure out how exactly.

 

Maybe the following will help: tweaking.com's Windows Repair (All in One), Safe Mode with Networking, clicking items 26 & 27 along with anything mentioning permissions, Restarting once if not twice, letting Windows come to full desktop.

 

I have one computer that has 2 data HDD's. I rotate between W10AU with W10 insider SDD's for the OS. If by chance I forget to remove the HDD's when W10 insider is used or updated, the installation will stop and request to scan one of the HDD's for errors. Often it will tell me that the recycle bin has been corrupted in the process. So when I update/use an insider version, I remove the HDD's and use a portable USB drive. This seems to work. If I forget to disconnect the portable USB drive and insert the W10AU, the portable will report corruption in the recycle bin. Twice in the past, one HDD became "RAW". There is a reason why this does this, I just can't put my finger on it yet. As long as the drives stay with the OS, everything is ok.