Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Windows Update broken


  • Please log in to reply
9 replies to this topic

#1 NickoG

NickoG

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:07:45 AM

Posted 14 June 2016 - 04:41 AM

Hello, guys. I'm having a problem with WU. I've interrupted Windows 10 installation and since then Windows Update does not search for new updates. It shows  "Upgrade to Windows 10 is ready" notification all the time and offers to reload computer to complete installation, but it doesn't change anything. I ran sfc /scannow and it found some errors: 

 
2016-06-13 23:45:33, Info                  CSI    000006ca [SR] Repairing 1 components
2016-06-13 23:45:33, Info                  CSI    000006cb [SR] Beginning Verify and Repair transaction
2016-06-13 23:45:33, Info                  CSI    000006cd [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
2016-06-13 23:45:33, Info                  CSI    000006cf [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
2016-06-13 23:45:33, Info                  CSI    000006d1 [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
2016-06-13 23:45:33, Info                  CSI    000006d2 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2016-06-13 23:45:33, Info                  CSI    000006d4 [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
2016-06-13 23:45:33, Info                  CSI    000006d5 [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3068708~31bf3856ad364e35~amd64~~6.1.1.0.3068708-814_neutral_GDR"
2016-06-13 23:45:33, Info                  CSI    000006d7 [SR] Repair complete
2016-06-13 23:45:33, Info                  CSI    000006d8 [SR] Committing transaction
2016-06-13 23:45:33, Info                  CSI    000006dc [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction  have been successfully repaired
     
    I don't know how to repair it and need your help. I've also run CheckSur (ver. 26) and it does not detect any errors... Also, I've tried different Microsoft tools to repair Windows Update automatically. No luck there as well. 
   What would you suggest, guys?
 
 P.S. Sorry for poor English. I'm not a native speaker. 
 
Edit: I've run built-in CheckSur for Windows 7 and it found some errors:
 
Checking Windows Servicing Packages
 
Checking Package Manifests and Catalogs
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~neutral~~11.2.9412.0.mum does not match the actual file name
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-Russian~31bf3856ad364e35~~~11.2.9412.0.mum Expected file name Microsoft-Windows-IE-Hyphenation-Parent-Package-Russian~31bf3856ad364e35~neutral~~11.2.9412.0.mum does not match the actual file name
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~neutral~~11.2.9412.0.mum does not match the actual file name
(f) CBS MUM Corrupt 0x00000000 servicing\Packages\Microsoft-Windows-IE-Spelling-Parent-Package-Russian~31bf3856ad364e35~~~11.2.9412.0.mum Expected file name Microsoft-Windows-IE-Spelling-Parent-Package-Russian~31bf3856ad364e35~neutral~~11.2.9412.0.mum does not match the actual file name
 
Checking Package Watchlist
 
Checking Component Watchlist
 
Checking Packages
 
Checking Component Store
 
Summary:
Seconds executed: 137
 Found 4 errors
  CBS MUM Corrupt Total count: 4
 
Unavailable repair files:
servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-Russian~31bf3856ad364e35~~~11.2.9412.0.mum
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.mum
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-Russian~31bf3856ad364e35~~~11.2.9412.0.mum
servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat
servicing\packages\Microsoft-Windows-IE-Hyphenation-Parent-Package-Russian~31bf3856ad364e35~~~11.2.9412.0.cat
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-English~31bf3856ad364e35~~~11.2.9412.0.cat
servicing\packages\Microsoft-Windows-IE-Spelling-Parent-Package-Russian~31bf3856ad364e35~~~11.2.9412.0.cat
 

Edited by NickoG, 14 June 2016 - 05:44 AM.


BC AdBot (Login to Remove)

 


#2 Willy22

Willy22

  • Members
  • 945 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Planet Earth
  • Local time:05:45 AM

Posted 14 June 2016 - 12:00 PM

- I am not surprised to see that WU doesn't work anymore. Interrupting of such a large installation (we're talking about 4 GB) and trying to revert that installation (??) is very dangerous. Too many things can go wrong.

- Did you upgrade or did you do a fresh clean install of Win 10 ? I would strongly recommend to do a fresh clean install. Saves A LOT OF hassle.



#3 NickoG

NickoG
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:07:45 AM

Posted 14 June 2016 - 12:12 PM

I see your point, but It had started installation without my permition and I freaked out  :huh:   :nono: .

I did not upgrade to Win 10 and not going to.



#4 Willy22

Willy22

  • Members
  • 945 posts
  • OFFLINE
  •  
  • Gender:Not Telling
  • Location:Planet Earth
  • Local time:05:45 AM

Posted 14 June 2016 - 01:07 PM

- I fear the simplest solution is to re-install Win 7. Computer repair shop ? Perhaps they're willing to give/sell you a copy of the Win 7 installation file(s) as well.

- Did you make a image of the system somewhere in the past ? Then you can re-install that image.

- Make sure to untick/uncheck the option ''Give me recommended updates the same way as important updates'' in the Windows 7 Update settings. Don't let WU install all Updates automatically.



#5 NickoG

NickoG
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:07:45 AM

Posted 14 June 2016 - 01:28 PM

Yeah, if I don't find another solution, re-installing will be the only option.



#6 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,612 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:09:45 PM

Posted 14 June 2016 - 01:53 PM

The sfc /scannow errors are known errors that were the result of a Microsoft update.  These have been around for over a year now.  These are not files that you need to worry about.  Microsoft created updates which resolved these.  The on update was the KB 3022345.  This is responsible for the utc.app.json and telemetry.ASM-WindowsDefault.json "errors" seen in the sfc /scannow.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#7 NickoG

NickoG
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:07:45 AM

Posted 14 June 2016 - 02:19 PM

Ok, thank you. But what about CheckSur log?



#8 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,612 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:09:45 PM

Posted 15 June 2016 - 09:11 AM

Are you having problems with updates?

 

From what I've found searching these errors  it does appear that these are false positives.


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 


#9 NickoG

NickoG
  • Topic Starter

  • Members
  • 14 posts
  • OFFLINE
  •  
  • Local time:07:45 AM

Posted 15 June 2016 - 09:30 AM

Are you having problems with updates?

 

From what I've found searching these errors  it does appear that these are false positives.

 

All problems solved  :) . Thank you for your help!



#10 dc3

dc3

    Bleeping Treehugger


  • Members
  • 30,612 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Sierra Foothills of Northern Ca.
  • Local time:09:45 PM

Posted 15 June 2016 - 09:36 AM

You are very welcome. :thumbup2:


Family and loved ones will always be a priority in my daily life.  You never know when one will leave you.

 

 

 

 





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users