Windows 7 upgrade to 10 error 0x8007001F - 0x3000D

zbook said:

Also see if this file is available:
C:\$WINDOWS.~BT\Sources\Diagnostics\diagnostics.dat

I'm working on compiling the other files, but here's this one.

- - - Updated - - -

zbook said:

Yes, same as post #25

Ok, I did a comprehensive job, which means a lot of files. In many cases, there were multiple files with a given name, so I set up a directory structure on my Google drive to match the source directories--each file is in a directory that matches its source directory on my C: drive. The top directory is here. MigLog.xml is here.

I hope this makes dealing with the files more rather than less straightforward--please let me know if there is a better way to do it.

zbook said:

Code:

0x8007001F, 0x3000D


2020-02-04 21:40:33, Error                 SP     CSetupPlatformOSSwitchCheckpoint::Rollback: Deleting of "C:\Windows.old" directory failed.[gle=0x00000091]

2020-02-04 21:38:50, Error                        MigApply caught exception: Win32Exception: Can't switch to requested user context: USER00000002.: A device attached to the system is not functioning. [0x0000001F] int __cdecl Mig::CKnowledgeManager::Apply(class Mig::CPlatform *,class Mig::CPlatform *,class Mig::CPlatform *,class Mig::CUserMappingList *,class UnBCL::Hashtable<class UnBCL::String *,class UnBCL::String *> *,class Mig::CAgentManager *,class Mig::CMigrationLogger *,int *,struct IMigExecuteProgress *)

I'm running out of ideas to fix the upgrade failure.
The next option may be to consider the backup plans: see post #4



Create a new user named test:

Open administrative command prompt and type or copy and paste:

net user test /add

Reboot

Sign on with the new user named test.

Place the computer in clean startup:
Troubleshoot Application Conflicts by Performing a Clean Startup - Windows 7 Help Forums

Reboot

Detach all hardware including any external drives.

Perform an upgrade.

If if fails then post a new setupdiag.




An additional option:

With a backup image some trial and error steps can be attempted:

a) Make an additional copy of Windows.old
b) Then delete Windows.old and $Windows.~BT folders


Delete Windows.old Folder in Windows 10
How to Delete the Windows.old folder in Windows 7/8/10






Maybe @dalchina has additional ideas.

One thing: my eye is pretty much untrained here, but my hunch is that having installed my user directory to the E: rather than C: drive might be at issue. The 'Windows.old' directory is not on the C: drive; it's on the E: drive:



I'll try some of this other stuff.

That could be the main problem as there were entries in the Panther logs.

Dalchina may have windows on one drive and users on another.
He had not mentioned any Windows upgrade problems.

Try:
1) upgrading with a new user
2) upgrading after deleting windows.old and ~BT or making sure there is only one the windows drive attached during the uprade

zbook said:

only one the windows drive attached during the uprade

Are you suggesting I attempt to upgrade with my E: drive disconnected?

That is a trial and error step, especially with the new user named test.

Ztruker said:

New user test won't have anything on the E: drive so it should not be a problem to disconnect that drive.

This is something I'm wondering about--to my knowledge, new user accounts also set up automatically on my E: drive. Is there are way to change this?

- - - Updated - - -

Ztruker said:

New user test won't have anything on the E: drive so it should not be a problem to disconnect that drive.

So here's the deal: my 'ProfilesDirectory' setting in the registry is 'E:\Users'. (See Windows Registry Hacks/HKEY LOCAL MACHINE - Wikibooks, open books for an open world). This must be what I modified (it was long ago) when I installed Windows 7. I don't know what effect changing this now would have, but because of that setting, newly created accounts are also created in the E:\Users directory.

zbook said:

That could be the main problem as there were entries in the Panther logs.

Dalchina may have windows on one drive and users on another.
He had not mentioned any Windows upgrade problems.

Try:
1) upgrading with a new user
2) upgrading after deleting windows.old and ~BT or making sure there is only one the windows drive attached during the uprade

Before I give a final update on this case, I want to thank everybody who gave suggestions. It's kind of hard to believe that a forum that gives free, tailored, well-informed advice to strangers exists on the internet. Thank you all very, very much.

Here are the steps that I took on my successful upgrade attempt. I don't know which of these steps is necessary or sufficient to complete the upgrade, but in case they prove useful to anyone else:

1. I edited the registry entry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList\ProfilesDirectory. It was set to a directory on my E: drive (Windows 7 was installed on my C: drive). I set it to "C:\Users".
2. I created a new user with administrator permissions. That user's User directory appeared on my C: drive.
3. I logged out of all accounts other than the new one, and attempted the upgrade. All hard drives, including the E: drive, remained connected.
4. I unplugged my network cable after the Windows 10 download to skip the 'looking for upgrades' phase.
5. (I did not delete windows.old or windows~BT before attempting this.)

If it would be useful for anyone to see any files from my successful upgrade, I'll be happy to share them--just let me know.