[SOLVED] No Updates installed on this computer: Unable to run sfc /scannow in safemode

A

arkimpulse

Member
Joined
Jun 2, 2015
Posts
10
Hello Team!

I have run into a problem of No Updates are installed on this computer which resulted in trying sfc /scannow.

It would at first say: Beginning system scan. This process will take some time.

Then: Windows Resource Protection could not perform the requested operation.

Here is the SFCFix.txt

SFCFix version 2.4.4.0 by niemiro.
Start time: 2015-06-01 22:40:16.459
Microsoft Windows 7 Service Pack 1 - amd64
Not using a script file.








AutoAnalysis::
WARNING: Unicode Registry Corruption Detected: HKEY_LOCAL_MACHINE\COMPONENTS\DerivedData\Components\x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7
WARNING: Failed to backup registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-t..tivexcore.resources_31bf3856ad364e35_0.0.0.0_es-es_976703a2cecf8161.
CORRUPT: Failed to repair orphaned component "value name not identified" (x86_microsoft-windows-t..tivexcore.resources_31bf3856ad364e35_0.0.0.0_es-es_976703a2cecf8161) on component watchlist.










SUMMARY: Some corruptions could not be fixed automatically. Seek advice from helper or sysnative.com.
CBS & SFC total detected corruption count: 0
CBS & SFC total unimportant corruption count: 0
CBS & SFC total fixed corruption count: 0
SURT total detected corruption count: 6
SURT total unimportant corruption count: 0
SURT total fixed corruption count: 0
AutoAnalysis:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.4.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2015-06-01 22:41:11.241
----------------------EOF-----------------------


Thanks!
 

Attachments

Hi and welcome to Sysnative. Sorry for the delay. I'd like to collect one more log before we decide what to do. Please provide the following.

Step#1 - System Update Readiness Tool (SUR)
1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
Hi BrianDrab,

Thanks for your help.

Here is the log that is requested:

Checking System Update Readiness.
Binary Version 6.1.7601.22471
Package Version 26.0
2015-06-05 21:29


Checking Windows Servicing Packages


Checking Package Manifests and Catalogs


Checking Package Watchlist


Checking Component Watchlist
(f) CBS Watchlist Component Missing 0x80070002 x86_microsoft-windows-t..tivexcore.resources_31bf3856ad364e35_0.0.0.0_es-es_976703a2cecf8161 Package_89_For_KB294972~31bf3856ad364e35~amd64~~6.1.1.4 Package registry presence failed, possibly an orphaned package on package watchlist


Checking Packages


Checking Component Store
(f) CSI Payload File Missing 0x00000000 rdpcorets.dll amd64_microsoft-windows-r..s-regkeys-component_31bf3856ad364e35_6.1.7601.18465_none_8d7f08131e967858
(f) CSI Corrupt Component Keyform 0x00000000 identity amd64_microsoft-winDows-cdosys.resoUrces_31bf3856ad364e35_6.1.7600.16385_he-il_a2e23717b50918a0 identity and keyform do not match; keyform is wrong.
(f) CSI Corrupt Identity 0xC0150016 Microsoft-Windows-Networking-Internet_Authentication_Service_IaSsam, CuLture=neUtral, VErsion=6.1.7600.6385, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=x86, versiOnScope=NonSxS x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7 Bad identity
(f) CSI Could Not Open file 0x0000007B winsxs\Manifests\x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7.manifest x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7.manifest x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7.manifest x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7.manifest x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7.manifest x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7.manifest x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7.manifest x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7.manifest x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7.manifest x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7.manifest x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7.manifest x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7.manifest x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7.manifest x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7.manifest x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7.manifest x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7.manifest x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7.manifest x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7
(w) CSI Replacement File: CreateFile Failed 0x0000007B winsxs\Manifests\x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7.manifest x86_microsoft-windows-n..tion_service_iassaM_31bf3856ad364e5_6.1.7600.1638_none_7b85b9b5b50dd8f7


Summary:
Seconds executed: 199
Found 5 errors
CSI Could Not Open file Total count: 1
CSI Corrupt Component Keyform Total count: 1
CSI Corrupt Identity Total count: 1
CSI Replacement File: CreateFile Failed Total count: 17
CSI Payload File Missing Total count: 1
CBS Watchlist Component Missing Total count: 1
Customer Experience report successfully uploaded. Thank you for participating. For more information, see the Microsoft Customer Experience Improvement Program on the Microsoft web site.


Thanks!
 

Attachments

There are some errors here that I've never seen. This will be interesting. I need copies of two of your registry hives in order to proceed. Please do the following.

Retrieve Components/Software Hives

  • Please download the Freeware RegBak from here: Acelogix Software - Download products
     You will find it at the bottom of the page that the link brings you to.
  • Go ahead and install this program and accept all the defaults. After the last install screen the program should open.
  • Click the New Backup button. Accept the defaults and simply click Start.
  • When it says Finished successfully, click the Close button.
  • This will bring you back to the main screen of the program. You will see one entry in this list with the date that you did it. Right-click on this line-item and select Explore Backup...
  • This will bring you into the folder where the backup was made. You should see a Users folder and a Windows folder along with a couple other files. Double-click on the Windows folder to open it. Then open the System32 folder and then config folder. You should see around 6 files in here, two of which are named COMPONENTS and SOFTWARE.
  • Copy these two files to your Desktop. If the COMPONENTS file does not exist, please fetch it instead from C:\Windows\System32\config\COMPONENTS.
  • Now right click on these files on your desktop and select Send to > Compressed (zipped) folder.
  • Then please upload the zip file(s) to your favourite file sharing website (it will be too big to upload here). Examples of services to upload to are Dropbox or One Drive or SendSpace and then just provide the link in your reply.
  • You can close any open windows you have as well as the RegBack program now.
 
Hi,

I've followed the required steps and I could only find the COMPONENTS file in the folder specified. Here is the link.

Capture.JPG

Thanks!
 
I believe I fixed all your issues. Here's what we need to do. Part of this is going to take coordination between us as well.

Step#1 - SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.

  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCFix.zip, and save this to your Desktop. Ensure that this file is named SFCFix.zip - do not rename it.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCFix.zip.
  5. Drag the file SFCFix.zip onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please

Step#2 - Replace Components Hive
1. Download COMPONENTSNEW.ZIP and save to your desktop.
2. Right-click on it and select Extract all.... Make sure the "Show extracted files when complete" is checked and click Extract.
3. Now we have the COMPONENTS file that we will be using to replace your current one.
4. Navigate to C:\Windows\System32\config
5. Right-click on the current COMPONENTS file and select rename. Rename it to COMPONENTS.bad.
Note: If you get an error that the file is in use, reboot your computer and then try again.
6. Take the file from the COMPONENTSNEW folder on your desktop and paste it into C:\Windows\System32\config

Step#3 - Replace Software Hive
I see the corruption within your Software hive. This hive is a bit more volatile than the Components hive. So we need to plan a time where we are both online. I'll need you to send me a current copy. I'll fix it and send it back to you within 15 minutes. And then you will have to replace your current hive. As I don't know your time zone (I'm Eastern, UTC -4), please let me know when you will be available to do this.
 

Attachments

I believe I figured out an easier way to fix the Software hive. After you perform Step1 & 2 from the previous post, rename the SFCFix.txt on your desktop to SFCFix1.txt and then please continue on with these steps.

Step#1 - SFCFix Script
Warning: this fix is specific to the user in this thread. No one else should follow these instructions as it may cause more harm than good. If you are after assistance, please start a thread of your own.
  1. Download SFCFix.exe (by niemiro) and save this to your Desktop. If you still have this on your desktop from downloading previously, you don't need to re-download.
  2. Download the file below, SFCScript.txt, and save this to your Desktop.
  3. Save any open documents and close all open windows.
  4. On your Desktop, you should see two files: SFCFix.exe and SFCScript.txt.
  5. Drag the file SFCScript.txt onto the file SFCFix.exe and release it.
  6. SFCFix will now process the script.
  7. Upon completion, a file should be created on your Desktop: SFCFix.txt.
  8. Copy (Ctrl+C) and Paste (Ctrl+V) the contents of this file into your next post for me to analyse please. Note: So you will be posting the contents of SFCFix1.txt from Step#1 of the previous post and SFCFix.txt from this post.
 

Attachments

Last edited by a moderator:
Hi BrianDrab,

I've followed your steps above and here are the results:

SFCFix1.txt

SFCFix version 2.4.4.0 by niemiro.
Start time: 2015-06-07 00:17:12.857
Microsoft Windows 7 Service Pack 1 - amd64
Using .zip script file at E:\Users\Richard\Desktop\SFCFix.zip [0]








PowerCopy::
Successfully took permissions for file or folder C:\Windows\winsxs\amd64_microsoft-windows-r..s-regkeys-component_31bf3856ad364e35_6.1.7601.18465_none_8d7f08131e967858


Successfully copied file E:\Users\Richard\AppData\Local\niemiro\Archive\winsxs\amd64_microsoft-windows-r..s-regkeys-component_31bf3856ad364e35_6.1.7601.18465_none_8d7f08131e967858\rdpcorets.dll to C:\Windows\winsxs\amd64_microsoft-windows-r..s-regkeys-component_31bf3856ad364e35_6.1.7601.18465_none_8d7f08131e967858\rdpcorets.dll.


Successfully restored ownership for C:\Windows\winsxs\amd64_microsoft-windows-r..s-regkeys-component_31bf3856ad364e35_6.1.7601.18465_none_8d7f08131e967858
Successfully restored permissions on C:\Windows\winsxs\amd64_microsoft-windows-r..s-regkeys-component_31bf3856ad364e35_6.1.7601.18465_none_8d7f08131e967858
PowerCopy:: directive completed successfully.








Successfully processed all directives.
SFCFix version 2.4.4.0 by niemiro has completed.
Currently storing 1 datablocks.
Finish time: 2015-06-07 00:17:13.020
Script hash: LI3Oz/1O/synLEyYe+m5avyYemPwhCWzf5r6B4UyUWg=
----------------------EOF-----------------------


SFCFix.txt

SFCFix version 2.4.4.0 by niemiro.Start time: 2015-06-07 00:28:37.482
Microsoft Windows 7 Service Pack 1 - amd64
Using .txt script file at E:\Users\Richard\Desktop\SFCScript.txt [0]








RegistryScript::
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-t..tivexcore.resources_31bf3856ad364e35_0.0.0.0_es-es_976703a2cecf8161.
Successfully took ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect.


WARNING: Failed to create backup for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-t..tivexcore.resources_31bf3856ad364e35_0.0.0.0_es-es_976703a2cecf8161.


Successfully deleted registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-t..tivexcore.resources_31bf3856ad364e35_0.0.0.0_es-es_976703a2cecf8161.
Successfully imported registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-t..tivexcore.resources_31bf3856ad364e35_0.0.0.0_es-es_976703a2cecf8161.


Failed to open registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-t..tivexcore.resources_31bf3856ad364e35_0.0.0.0_es-es_976703a2cecf8161 with error code ERROR_FILE_NOT_FOUND.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect\x86_microsoft-windows-t..tivexcore.resources_31bf3856ad364e35_0.0.0.0_es-es_976703a2cecf8161.
Successfully restored ownership and permissions for registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Component Based Servicing\ComponentDetect.
RegistryScript:: directive failed to complete successfully.








Failed to process all directives successfully.
SFCFix version 2.4.4.0 by niemiro has completed.
Currently storing 3 datablocks.
Finish time: 2015-06-07 00:28:37.587
Script hash: ptPx8cNMwZ3GwESWzV+3CEdEEZ48MmxoxozsgXhjUXQ=
----------------------EOF-----------------------


Also, I'm in MDT -6 Time Zone, I guess we can work something out....
 
Logs look good. As long as you were able to successfully replace the COMPONENTS hive please do the following.

Step#1 - System Update Readiness Tool (SUR)
1. Download and run the following file.
2. When it asks you if you wish to install, please answer yes. Note: It could take 15 minutes or more to run. Please don't cancel.
3. You will get an Installation Complete screen when it's done running.
4. Please attach the log from the following location. C:\Windows\Logs\CBS\CheckSUR.log
Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
Thank you. All corruption was fixed from that log. For good measure I would like you to do the following.

Step#1 - SFC Scan


  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.

Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
Thank you. There were a few corruptions that said they were fixed but the following one in particular concerns me as explorer.exe is critical to the general operation of your machine. As a result I'm going to have you run this again to be certain this file was replaced with a good copy. Please ensure you reboot your machine and then follow the instructions again below.

Code: 
2015-06-07 23:14:38, Info                  CSI    0000051c Hashes for file member \??\C:\Windows\explorer.exe do not match actual file [l:24{12}]"explorer.exe" :
  Found: {l:32 b:OfXloV6cCN6ZmPNh7Gbi/A07Vxci8qb7LkZq1OUSHQc=} Expected: {l:32 b:a+0aOpVqhZ70Qg/rJGbAQIAOrwHvUyFO+dq1Ou/xz/A=}
2015-06-07 23:14:38, Info                  CSI    0000051d [SR] Repairing corrupted file [ml:520{260},l:28{14}]"\??\C:\Windows"\[l:24{12}]"explorer.exe" from store

Step#1 - SFC Scan



  1. Click on the Start
    Start%20Orb.jpg
    button and in the search box, type Command Prompt
  2. When you see Command Prompt on the list, right-click on it and select Run as administrator
  3. When command prompt opens, copy and paste the following commands into it, press enter after each

    sfc /scannow

    Wait for this to finish before you continue

    copy %windir%\logs\cbs\cbs.log %userprofile%\Desktop\cbs.txt
  4. This will create a file, cbs.txt on your Desktop. Please attach this to your next post.


Please Note:: if the file is too big to upload to your next post please upload via a service such as Dropbox or One Drive or SendSpace and just provide the link.
 
You are clean. The final corruption mentioned in your logs is benign and a known issue. More info follows. Can you try Windows Update now? It should work.

Code: 
Line 793102: 2015-06-08 22:50:01, Info                  CSI    00000436 [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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 793112: 2015-06-08 22:50:01, Info                  CSI    00000438 [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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 793650: 2015-06-08 22:50:01, Info                  CSI    0000043a [SR] Cannot repair member file [l:24{12}]"utc.app.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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 793652: 2015-06-08 22:50:01, Info                  CSI    0000043b [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3022345~31bf3856ad364e35~amd64~~6.1.1.2.3022345-814_neutral_GDR"
 Line 793661: 2015-06-08 22:50:01, Info                  CSI    0000043d [SR] Cannot repair member file [l:66{33}]"telemetry.ASM-WindowsDefault.json" of Microsoft-Windows-Unified-Telemetry-Client, Version = 6.1.7601.18839, 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 793663: 2015-06-08 22:50:01, Info                  CSI    0000043e [SR] This component was referenced by [l:162{81}]"Package_250_for_KB3022345~31bf3856ad364e35~amd64~~6.1.1.2.3022345-814_neutral_GDR"
 Line 793743: 2015-06-08 22:50:01, Info                  CSI    00000441 [SR] Could not reproject corrupted file [ml:520{260},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:24{12}]"utc.app.json"; source file in store is also corrupted
 Line 793748: 2015-06-08 22:50:01, Info                  CSI    00000444 [SR] Could not reproject corrupted file [ml:520{260},l:114{57}]"\??\C:\ProgramData\Microsoft\Diagnosis\DownloadedSettings"\[l:66{33}]"telemetry.ASM-WindowsDefault.json"; source file in store is also corrupted

https://support.microsoft.com/en-us/kb/3022345


quote_icon.png
Originally Posted by Microsoft
This update enables the Diagnostics Tracking Service in Windows 8.1, Windows Server 2012 R2, Windows 7 Service Pack 1 (SP1), and Windows Server 2008 R2 SP1. This tracking service collects data about functional issues in Windows.

This update contains the following two manifests that are occasionally updated by the Diagnostic Tracking Service:

telemetry.ASM-WindowsDefault.json
utc.app.json

The two files are marked as static files in the update. When an advanced user runs the System File Checker Tool (sfc.exe), the files are unintentionally flagged as corrupted. There is no impact or corruption on a device that is running this update, and this issue will be fixed in a later service update.
Click to expand...
 
Hi BrianDrab,

Looks great! Working normally now. Thank you very much for your support! Updates show up now too.
 
You must log in or register to reply here.

Has Sysnative Forums helped you? Please consider donating to help us support the site!

Back
Top