Windows 10 upgrade reverts back to Windows 7 Home Premium (previous OS

keokat15 · 13 Aug 2015

Hello everyone, I've been stuck on trying to upgrade to Windows 10. I am currently using a OEM Windows 7 Home Premium 64 bit, HP Pavilion dv6 laptop.

Problem started when I notified Microsoft that I wanted to upgrade to Windows 10. I upgraded with my wife's laptop first. She also has the same laptop, but its a newer version. Windows 10 installed fine, so I decided to do mine. So I repeated the steps I did when I upgraded my wife's laptop. I clicked on the Windows icon in my task bar. It told me Windows upgrade was ready, so I clicked on continue. I let the update take its course. After 8 hours of seeing the words "working on it" I decided to exit out of the program, thinking something is wrong. I restarted my laptop and clicked on the Windows icon again. This time I did this before I went to bed. When I woke up it still had the words "working on it." So I did some research and I came across a thread that stated to use Windows update. I ran the Windows update and to my surprise Windows 10 was there (it was the only update). I clicked on update and it started to download, so I figured life was good. Windows 10 downloaded and installed. It went through the three phases (Baking up files, installing software and drivers, and then validation)<--if those are not the exact three phases I forgot, but there are three phases-->as soon as the third phase finished it states that something goes wrong and reverts back to Windows 7 Home Premium. So I commence my research, I download every fix it tool known to man and every SUR that all the forums point to. I will post my SFC /scannow file in this thread. So I contact Microsoft and the first technician was helpful, he thought my problem was that my profile was corrupt, so we created a new administrator profile and tried installing the update that way, but still my laptop does the same thing, goes through the update and install then reverts back to original OS. So I research some more because I don't want to wait 2 hrs on the phone to talk to another Microsoft technician. So I do more research. I came across a thread to do a clean boot and turn off WIFI when during the install phase of Windows 10. I did this, but instead of turning of WIFI I cut my router off so there was no Internet period! Laptop still reverted back to original OS. So I did more digging and came across another thread that states to run the update troubleshooter. So I open help in windows and download the update troubleshooter and attached is my result. I have also uploaded my CBS log. Since I got frustrated I decided to give Microsoft another chance, so I waited two hours to talk to a technician. Technician decided to download Windows 10 using the media creation tool. I thought it was going to work. I waited patiently as I saw my Windows 10 software being downloaded. Once it downloaded it started to install, so I was pretty excited. But after the last part of the installation it went to check for updates and about 15 minutes later it stated that windows had a problem and it couldn't upgrade. Please any help would be appreciated. I don't know what else to do at this point.

Thanks for your time to read this post

ignatzatsonic · 13 Aug 2015

Did you begin this extravaganza with Windows 7 Home Premium?

Or Windows 7 Home Premium SP 1?

What's an "SUR"?

NoelDP · 13 Aug 2015

Please post the CheckSUR.log file
(SUR aka SURT aka CheckSUR - the System Update Readiness Tool)
There is no SFC data in your CBS.log - and no errors in the background CBS data. Please post a couple of the latest CBSPersist files.

keokat15 · 13 Aug 2015

@ignatzatsonic-good question and sorry for not posting that earlier. SP1 was preinstalled. Also my laptop was bought with Windows 7 Home Premium SP1 already installed.

@NoelDP-Thanks for answering ignatzatsonic and also here is another file that "I think" you are asking for. I don't know if you care but I add the CheckSUR.persist.log file. I don't what that is but it looks important.

Thanks for your help as always

NoelDP · 13 Aug 2015

Here's the summary from the CheckSUR log -

Code:

Summary:
Seconds executed: 425
 Found 6 errors
 Fixed 6 errors
  CBS MUM Missing Total count: 6
  Fixed: CBS MUM Missing.  Total count: 6
  Fixed: CBS Paired File.  Total count: 6

The CheckSUR.Persist.log is interesting - it apparently shows that you've just installed IE11 despite having some errors in the IE10 install.

It's the first time I've seen some of these particular errors fixed - and in quite a clever way, at that! (deleting the problem files and allowing CheckSUR to re-insert them - because CheckSUR accepts the files as being genuine for replacement purposes so refuses to do the proper work it needs to do)
Where did you get that idea from?

SO we now have a clear CheckSUR log -

Please run another SFC /SCANNOW and post the new CBS.log file

keokat15 · 13 Aug 2015

@NoelDP- The funny thing was it was a fluke and I can't take credit for that. When I saw those errors I went to the folder where they were located and just deleted them. After researching 80070057 fail it told me to the CheckSUR as stated above. So honestly that was a fluke. I'm running an SFC /scannow and I will post when its finish.

keokat15 · 13 Aug 2015

@NoelDP- My CBS file is too large for the forum.

keokat15 · 13 Aug 2015

@NoelDP- I was able to make the file a zip file so here is the CBS log.

NoelDP · 13 Aug 2015

The only errors in the SFC data are these...

Code:

	Line 16539: 2015-08-13 22:46:12, Info                  CSI    0000035c [SR] Repairing 1 components
	Line 16540: 2015-08-13 22:46:12, Info                  CSI    0000035d [SR] Beginning Verify and Repair transaction
	Line 16543: 2015-08-13 22:46:12, Info                  CSI    0000035f [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
	Line 16546: 2015-08-13 22:46:12, Info                  CSI    00000361 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18869, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch

They are 'normal' and don't cause problems - MS will get around to fixing them some day (so they say)

So that means that there's not a lot wrong with the system as such.

Did you check that there were no software compatibility problems before starting the update, by clicking on the notification icon? if there were/are any you must address these first.

keokat15 · 13 Aug 2015

@NoelDP-I tried everything. I wanted to reinstall Windows 7 but my key was not valid so I called Microsoft and it because this is an OEM Laptop, but besides that point the only update I have is the Windows 10 and it will not install period. I get these two errors that I just can't figure (C1900101-4000D and 80070057) out even searching online doesn't help. I get the C1900101-4000D when Windows tries to install Windows 10 and it reverts back then the update screen produces this error. When I run the update troubleshooter it fixes everything but can't repair 80070057. Also the weird thing is that my update just updated 32 Microsoft Office components that I don't have on this laptop (weird). Don't know what else to do. Microsoft Techs can't help either! So I'm basically stuck. Any advice would help.