Windows 10 Error upgrading from win7 to win10

[PaulSp]

The upgrade fails with a message "x80070005-x2000A error in SAFE_OS phase of PREPARE_FIRST_BOOT operation.
In the setupact.log, I've located the error(s), but I don't know what the problem is. The following is an excerpt from the setupact.log containing the error:

2019-07-13 21:42:42, Info SP CRelocateOS: Moving new OS piece from D:\$WINDOWS.~BT\NewOS\ProgramData to D:\ProgramData
2019-07-13 21:42:42, Info SP VERBOSE: Path D:\$WINDOWS.~BT\NewOS\ProgramData has no exceptions, trying a straight move
2019-07-13 21:42:42, Info SP VERBOSE: Successfully moved (1) D:\$WINDOWS.~BT\NewOS\ProgramData to D:\ProgramData
2019-07-13 21:42:42, Info SP CRelocateOS: Moving new OS piece from D:\$WINDOWS.~BT\NewOS\Users to D:\Users
2019-07-13 21:42:42, Info SP VERBOSE: Path D:\$WINDOWS.~BT\NewOS\Users has no exceptions, trying a straight move
2019-07-13 21:42:42, Info SP VERBOSE: Successfully moved (1) D:\$WINDOWS.~BT\NewOS\Users to D:\Users
2019-07-13 21:42:42, Info SP CRelocateOS: Moving new OS piece from D:\$WINDOWS.~BT\NewOS\Windows to D:\Windows
2019-07-13 21:42:42, Info SP VERBOSE: Path D:\$WINDOWS.~BT\NewOS\Windows has no exceptions, trying a straight move
2019-07-13 21:42:42, Warning SP SPMoveFileWithShortName: Failed to move D:\$WINDOWS.~BT\NewOS\Windows to D:\Windows, error: 0x00000005
2019-07-13 21:42:42, Error SP CRelocateOS: Cannot move path D:\$WINDOWS.~BT\NewOS\Windows from Windows.NEW. Error: 0x00000005[gle=0x00000002]
2019-07-13 21:42:42, Info SP SetupPlatform: Global progress: 29, Phase progress: 97
2019-07-13 21:42:42, Error SP Operation failed: Relocate OS from D:\$WINDOWS.~BT\NewOS to D:\. Error: 0x80070005[gle=0x000000b7]
2019-07-13 21:42:42, Error SP Operation execution failed: 10. hr = 0x80070005
2019-07-13 21:42:42, Error SP ExecuteOperations: Failed execution phase Safe OS. Error: 0x80070005
2019-07-13 21:42:42, Error SP CSetupPlatformPrivate::Execute: Execution of operations queue failed, abandoning. Error: 0x80070005
2019-07-13 21:42:42, Info Persisting diagnostics data to D:\$WINDOWS.~BT\Sources\Diagnostics\diagnostics.dat
2019-07-13 21:42:42, Info Diagnostics data saved successfully
2019-07-13 21:42:42, Info SP Execution phase [Safe OS] exiting with HRESULT [0x80070005]

Can anyone help?

 

[Neemobeer]

0x0005 is access denied. Do you have other drives, usb drives or sd cards plugged in? If so remove them.

 

[PaulSp]

No. This upgrade is from an .iso file on the DVD (D: ) drive. The only other drive is my C: drive, an SSD.

 

[Neemobeer]

Then we need to see the whole log and also the diagnostics.dat file

 

[PaulSp]

I'll attach the .zip file output from the SetupDiag.exe that I ran. It's over 2 MB. It contains the whole setupact.log file. The setupact.log file is 43 MB unpacked!

 

[PaulSp]

My .iso file was built from a Microsoft site and I've tried upgrading both from it and online directly, both giving the same results. As a former programmer/unix system administrator, I don't see any reason why having the destination drive being a SSD makes any difference to the software. The software doesn't know what kind of drive it is writing to. To me the issue is that Microsoft ought to be able to design their upgrade to work on a virtually vanilla Windows 7 system and error messages ought to provide enough info to fix any problems. Obviously their error messages leave a lot to be desired. Even the log files don't seemingly provide enough information. I don't know how anyone will be able to tell what the real problem is when the operation that is failing appears to be moving a whole directory from one location to another and having the operation fail with an "access denied" error. It seems that any one of the directories or files in the subtree could be the problem. How do we determine which one is the culprit? Is it possible that some file in the windows structure has improper permissions and this is causing the failure? It would be nice if Microsoft had a utility that traversed the windows system files and assigned the appropriate owner/permissions. It is possible that at some point I was trying to do something in the structure and modified the ownership so I could gain access to a particular file, but this would have been a text file, not a executable if that happened. I racked my brain and I don't remember needing to see anything in the windows directory tree.

Another data point is that this error happens AFTER a first boot of Windows 10 and it appears to occur applying further updates. The "working on updates" gets to about 29% before the upgrade aborts and reverts back to windows 7.

Of course a cold install should work, but that isn't what I want to do. I am wondering how many others have had similar issues. BTW, I am only doing this because Microsoft is ending support of Win7. I like Win7... it does everything I need, so if I didn't have to upgrade, I wouldn't.

Another thought -- could I reinstall my base copy of Windows 7 over my existing system without losing my current programs and files? This will obviously lose all of the updates over the years, but it wouldn't matter, would it, since I'd be upgrading to Win10 anyway? Doing this would insure all the system files would have proper ownership/permissions, wouldn't it?

 

[Neemobeer]

From reply 4 can you get the diagnostics.dat file that may have more detail as to the errors. A lot of Microsoft's errors are documented but can still be cryptic. The first 3 or 4 bits are not that important and usually 8 if it's a Microsoft error or C if it's third party. The next 12 are the subsystem generating the error and the last 16 bits are the error code. The actual error from your log dump is 0005 which is access denied

 

[PaulSp]

Here is the diagnostics.dat file...I had to change the extension to .txt because this forum would not allow attachment of a .dat file, for some reason.

 

[Neemobeer]

Hmm yeah didn't look too useful. It may be a code MS uses internally for diagnostics

 

[PaulSp]

If Microsoft wanted us to look at it, why would they make it a binary file, anyway. It must be intended to be read by some piece of diagnostic software.

 

[PaulSp]

Evidently, Windows 10 has a diagnostic tool which reads this (diagnostics.dat) file. I think it's called the Diagnostic Data Viewer!! Too bad it doesn't appear to have a Win 7 version. If you have a Win 10 system, you should be able to use that tool to see if it says anything useful...

Edit: reading a little further... maybe that tool isn't for this file.

 

[Neemobeer]

If you haven't you may want to check the disk health and run chkdsk and sfc on the source disk. Also if you still have it upload the setuperr.log file should be in the same directory as setupact.log

 

[PaulSp]

I have run both. Everything is fine. The setuperr.log file has nothing pertinent in it.

 

[PaulSp]

I am not familiar with your terminology. My current system is Windows 7 Pro with service pack 1. What do you mean by "full" version? And what do you mean by windows 10 "update" version? I am just trying to get to some level of Windows 10 pro. The May update can be dealt with later, once i get Windows 10 installed. Your first link appears to refer to problems with a Win10 system installing the May update. I don't think I'm at that level yet and none of those error messages stated there apply to me.
I don't know what a UserAgent is, let alone how to "spoof" it. My download for Win10 was an .iso file of less than 4 GB, fitting nicely on a standard DVD.

 

[PaulSp]

Sorry, your post may as well have been written in Greek. I don't understand it at all. You talk about a "FULL" version of win7 vs. an update version. Can you explain what that means and how I would determine this on my system? That is to say, how do I tell whether I have a "FULL" version vs. an "update" version of win7?

 

[PaulSp]

Ok. Windows 7 came installed on my Dell laptop at purchase (~2010), so I guess I have a
full version.
I'm still confused by your advice regarding downloading .iso files. I have already downloaded an .iso file and it is less than 4 GB in size. Is there something wrong with this .iso? You seem to be saying that somehow I can get to a different download site which will download a different .iso file. What is the difference between these two .iso files? How does one "spoof" the UserAgent?

 

[PaulSp]

Below is an excerpt from the beginning of the setupact.log file from the attempted install using the .iso file I talked about (< 4GB):

2019-07-14 15:37:57, Info MOUPG SetupHost: Setup build version is: 10.0.18362.1 (19h1_release.190318-1202)
2019-07-14 15:37:57, Info CONX Host OS version: 6.1.7601.1130 Service Pack 1 (1.0) Platform 0x2, SuiteMask 0x100, ProdType 0x1
2019-07-14 15:37:57, Info CONX Source OS: Host SKU Info: Edition = 'Professional', Edition Type = 'Client', Installation Type = 'Complete', Product Name = 'Windows 7 Professional', Arch = amd64, StationType = Client Workstation, Stage type = Staged Image
2019-07-14 15:37:58, Info MOUPG Host OS License State [ Genuine ]
2019-07-14 15:37:58, Info MOUPG Host OS Architecture [ x64 ]
2019-07-14 15:37:58, Info MOUPG Host OS Language Id [ 1033 ]
2019-07-14 15:37:58, Info MOUPG User UI Language Id [ 1033 ]
2019-07-14 15:37:58, Info MOUPG Host OS Edition [ Professional ]
2019-07-14 15:37:58, Info MOUPG Host OS Version [ 6.1.7601 ]
2019-07-14 15:37:58, Info MOUPG Host OS Build String [ 7601.24499.amd64fre.win7sp1_ldr.190612-0600 ]

It appears from what's in parentheses that this is release 1903. Is this not the May 2019 release?
I'll probably try the spoofing thing in a few days, if nothing else occurs to me, in order to get a different .iso file to try. Sounds like I'll have to burn it to a double-sided DVD, though.

 

[PaulSp]

Update! I have finally managed to upgrade my Win7 system to windows 10. Thanks to Spirit Wolfe for educating me on UserAgent spoofing. I spoofed the Windows site and first I downloaded the May 2019 .iso file. This failed exactly the same way my previous .iso did (the one I downloaded with the MediaCreationTool). I think it follows that the problem lies with the May 2019 upgrade release rather than the method of its download. However, spoofing gave me another option: downloading the October release. I did that and was successful in perform the upgrade.

Thanks to everyone who tried to help me, especially Spirit Wolfe.

 

[AdrianG001]

The upgrade fails with a message "x80070005-x2000A error in SAFE_OS phase of PREPARE_FIRST_BOOT operation.
In the setupact.log, I've located the error(s), but I don't know what the problem is. The following is an excerpt from the setupact.log containing the error:

2019-07-13 21:42:42, Info SP CRelocateOS: Moving new OS piece from D:\$WINDOWS.~BT\NewOS\ProgramData to D:\ProgramData
2019-07-13 21:42:42, Info SP VERBOSE: Path D:\$WINDOWS.~BT\NewOS\ProgramData has no exceptions, trying a straight move
2019-07-13 21:42:42, Info SP VERBOSE: Successfully moved (1) D:\$WINDOWS.~BT\NewOS\ProgramData to D:\ProgramData
2019-07-13 21:42:42, Info SP CRelocateOS: Moving new OS piece from D:\$WINDOWS.~BT\NewOS\Users to D:\Users
2019-07-13 21:42:42, Info SP VERBOSE: Path D:\$WINDOWS.~BT\NewOS\Users has no exceptions, trying a straight move
2019-07-13 21:42:42, Info SP VERBOSE: Successfully moved (1) D:\$WINDOWS.~BT\NewOS\Users to D:\Users
2019-07-13 21:42:42, Info SP CRelocateOS: Moving new OS piece from D:\$WINDOWS.~BT\NewOS\Windows to D:\Windows
2019-07-13 21:42:42, Info SP VERBOSE: Path D:\$WINDOWS.~BT\NewOS\Windows has no exceptions, trying a straight move
2019-07-13 21:42:42, Warning SP SPMoveFileWithShortName: Failed to move D:\$WINDOWS.~BT\NewOS\Windows to D:\Windows, error: 0x00000005
2019-07-13 21:42:42, Error SP CRelocateOS: Cannot move path D:\$WINDOWS.~BT\NewOS\Windows from Windows.NEW. Error: 0x00000005[gle=0x00000002]
2019-07-13 21:42:42, Info SP SetupPlatform: Global progress: 29, Phase progress: 97
2019-07-13 21:42:42, Error SP Operation failed: Relocate OS from D:\$WINDOWS.~BT\NewOS to D:\. Error: 0x80070005[gle=0x000000b7]
2019-07-13 21:42:42, Error SP Operation execution failed: 10. hr = 0x80070005
2019-07-13 21:42:42, Error SP ExecuteOperations: Failed execution phase Safe OS. Error: 0x80070005
2019-07-13 21:42:42, Error SP CSetupPlatformPrivate::Execute: Execution of operations queue failed, abandoning. Error: 0x80070005
2019-07-13 21:42:42, Info Persisting diagnostics data to D:\$WINDOWS.~BT\Sources\Diagnostics\diagnostics.dat
2019-07-13 21:42:42, Info Diagnostics data saved successfully
2019-07-13 21:42:42, Info SP Execution phase [Safe OS] exiting with HRESULT [0x80070005]

Can anyone help?

Error 0x80070005 occurs when you attempt to install system updates and you do not get the required permissions to do the operation. This is apparently on account of computer's security settings and policies. Supposing that you are logged in system as standard account instead of an administrator user

Switch user account to an administrator account

An administrator is the user who is allowed to make changes on computer and changes will influence other users of the PC. Administrator account is able to configure security settings, manage software, hardware and all files on the computer and make changes to other users. Some administrator account is password protected, and in that case you need to know the password to log on the account.

Step 1 The easiest way is to restart computer and log in with administrator account. If you do not want to restart computer, then you can switch user account to administrator with following steps.

Step 2 Click "Start" button and choose "Control Panel" on which you can see the "User Account" option. Click and open it.

Step 3 You can see all user accounts on the User Accounts window, and then please select the one that represents your user account. Go ahead and click "Change the account type" and enter password if required.

Step 4 Then log out Windows and log back in once again, after which you'll have the same access rights to all operations as administrator account. Then you can try installing Windows updates now.

Scan for malware and virus

If your computer has installed antivirus software, please make sure the software is always up to date. If you haven't had antivirus software installed on your computer, you can use Microsoft Safety Scanner which is freeware and can be used to scan system for computer viruses and malware. Though it's not full-featured software and can't provide real-time protection against virus, it can be used manually on a PC and scan computer which contains any potential infection

Step 1 Download Microsoft Safety Scanner from Microsoft website and get it installed on your computer following its installation instructions. Make sure you add a shortcut of Safety Scanner on desktop.

Step 2 Double-click the Safety Scanner shortcut icon on the desktop and get it started. Next click "Scan Type" and "Full Scan" in sequence and continue to click "Next".

Step 3 It starts scanning process and you need to wait for it to complete. This process may take some time and after the scan is done, you can remove all detected viruses or malware entries. Restart computer and try again to run Windows Update.

Fix network Errors

As to the error code 0x80070005 which happens to shared network resource, you need to alter sharing permissions of the folder in question:

Step 1 Find the shared folder on your computer and right-click it to view its Properties.
Step 2 Click the Security tab and select "Add" and "Advance". Click "Find now" and wait for a while and then choose "Everyone".
Step 3 Click "OK" to confirm and "Apply" to get settings applied. Then close the window and the folder will be shared to everyone who is able to connect to your network.

Regards,
Adrian