eSATA Data Disk Locks System Post Win10 Update-File Recovery Problem?

[baumgrenze]

I posted this on tenforums.com 4 hours ago. There have been no replies.

The reason for the 'dormancy' of the Win10 install is I preferred to continue to use Win7. As the end-of-life approaches I noticed articles suggesting that it might be wise to update my Win10 install so that my install is of a supported version.

I've subsequently established that both Win10 and Win7 lock up when I attempt to work with my data drive.

Is this a problem for file recovery software (suggestions) or perhaps simply CHKDSK. I hate to make a bigger mess randomly trying to see if anything might work.
.....

I installed Win10 in July 2016 and left it 'dormant' until yesterday, 1/25/19. I was concerned I might lose the ability to update it. It needed many updates.

I forgot to turn off my eSATA data drive before I ran the updates the first time I tried.

The update process created a new folder called "Windows10Upgrade" on the eSATA drive. It contains a new folder containing a 1.239 GB ESD file and a small XML Document. If I was asked permission, I certainly missed seeing it.

When I shut down Win10 and disconnected that System Disk and then rebooted from another System Disk into Win7Pro/x64 with the eSATA drive running my system locks up. If I start the drive after booting to Win7 I can see the file structure on the drive in Windows Explorer, but any attempt to use it locks up the system.

I returned on 1/26/19 and successfully ran the updates again with the eSATA drive turned off. I now have Ver. 1803 installed, so it appears that the update was successful. I never installed any program files on the system disk with Win10. I can see the folder in file explorer in Win10.

Win10 appears to recognize a problem with the eSATA disk and runs some kind of checking process on it, but I can't get my digital camera up quickly enough to document it before the two windows that describe it have vanished.

What might the process have done to my eSATA drive?

Would it help to delete the new folder and its contents? Perhaps do that and also run the Win10 version of CHKDSK afterwards?

I don't want to dig a deeper hole for myself.

thanks

baumgrenze
​

 

[samuria]

You say you haven't had a reply in 4 hours everyone works for free on the forums so you have to be patient we have lives to live. If ten is on 1803 it's way behind latest is 1809 any files or folders created by ten will be owned by the SID of ten and may be a system folder protected by the o/s

 

[Megahertz07]

For upgrading Win 10 from one version to the another a whole Win 10 setup is downloaded, then on a fresh boot, it will begin the installation. It will take hours to complete.
The installation files has been downloaded to the eSATA drive. You can delete all folders.
My suggestion is to do a check disk (under Win 7 or win 10)
Open a CMD window as admin (right click on the CMD shortcut and choose Run as administrator). Then type
chkdsk x: /f (replace x by the eSATA drive letter)

 

[baumgrenze]

I Included This to Acknowledge I'd Tried First on Tenforums

You say you haven't had a reply in 4 hours everyone works for free on the forums so you have to be patient we have lives to live. If ten is on 1803 it's way behind latest is 1809 any files or folders created by ten will be owned by the SID of ten and may be a system folder protected by the o/s

Thank you for your reply.

I included this information because it was not clear to me just where i should best post this problem, on sevenforums.com or on tenforums.com. I did not intend to express 'impatience' but to acknowledge that my tenforums.com post might be being seen as 'irrelevant' by the experts there.

I've uploaded 2 images. I apologize for using edited digital photos. I find it a 'sure way' to get a screen shot in an unfamiliar environment. I added the date/time stamp from Irfanview for each image.

Why is Windows 10 telling me that the installation has no available updates when it is at 1803 and not 1809. Is this worth a separate post on tenforums?

thanks
baumgrenze