Solved System Restore doesn't work

[glennc]

Good day,
I went to do a backup after last W7 update. The external SATA drive was not recognized. Found it inactive and without a drive letter and set them. Unit works on other computers with a USB. Ran a sfc /scannow with errors that couldn't be corrected. Attempted a restore which after reboot fails. Did a system image restore to a preupdate version (Paragon), apparently successfully. sfc still shows errors.
I am asking if I should go directly to the update section and do the MS download and gather the CBS.log?
Oh an of course lost the registration for the W10 download.
Thanks for pointing me in a correct direction!
glennc

 

[glennc]

Without any response, I went on with the Update thread on the SURT and CBS.logs. Then realized I might as well try and fix the latest Paragon System Image Restore (marked HopefulC:\). Got the Windows 10 registration back and my emails. Reran the SURT and sfc /scannow. sfc still indicating it has corrupted files...
Would appreciate any help!!
glennc

 

[DennisCPA]

If these are your errors after looking at the logs (see Bolded filenames):
-----------------------------------------------------------------------------------
(Info CSI 000001c1 [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).

(Info CSI 00000319 [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)
------------------------------------------------------------------------------------------------------

Then proceed as follows:

To remove the SCF error uninstall the KB3022345 Update

The good news is that the service is optional even though it is listed
as recommended on the system.
DiagTrack can be uninstalled easily. Proceed exactly as follows:




Control Panel > Program and Features > View Installed Updates

• Type KB3022345 in the search bar
• Wait until found (if not found than proceed to KB3068708 below)
• Select Uninstall.

(That did not solve the problem ... because KB3022345 was replace by KB3068708




Therefore I uninstalled KB3068708)

• Type KB3068708 in the search bar
• Wait until found
• Select Uninstall.

There are remnant files: diagtrackrunner.exe in two locations.

• C:\Windows\winsxs\amd64_microsoft-windows-a..xperience-inventory_31bf3856ad364e35_6.1.7601.18868_none_e83d75d9e59ba1ea
• C:\Windows\System32\CompatTel

Do not delete diagtrackrunner.exe in either location as SFC will ID the missing files

Also, there are two of three services that I stopped:
Start Services by Typing into the Search window: "services.msc" (not the quotation marks!)




Locate the following services as they are related

• Diagnostic Policy Service Automatic - Started (leave this alone)
• Diagnostic Service Host Stop it then Disable it
• Diagnostic System Host Stop it then Disable it

These issues may be the reason that you had the failures.

HTH
Dennis

 

[glennc]

Hello DennisCPA,
I will investigate your instructions and see if this indeed helps. Thank you for your time!
Much appreciated.
glennc

 

[glennc]

Howdy Dennis,
I uninstalled KB3022345 and ran sfc, still had issues. Then uninstalled KB3068708, sfc ran and gave 100% ok. Great and thanks. Microsoft Tech claimed that KB3068708 was an IMPORTANT update and that he would reinstall it.
What would happen if the services for diagtracker were not disabled and stopped? They were started and set as manual !!???
Since I manual set my external hardrive, will that be an issue?
Thanks for your time and knowledge
Appreciated
glennc

 

[DennisCPA]

Glennc,

I looked at the link and have no idea what changed the word "fix" into that link. If anyone finds out how that may have happened please post back.

Actually, when I looked at my post a few minutes after its post, I saw the underlined blue type and "assumed" it was an internal link and continued on.

Dennis

 

[DennisCPA]

glennc,

On two of my computers on which I had those installations, I originally deleted the two executable(s). Then SFC complained and I did a System Restore and Disabled the two listed Services. All is well for about a week (so far continues OK).

I did not want the chance that they would somehow "self-activate" and continue to monitor my keystrokes and other activity again. It is interesting that MS let this error continue without a fix (a fix should be extremely easy) since about June 6th. It almost seems like it was an alert to the knowing w/o admission of culpability.

BTW, I am still bugged about that "fix" link. (I believe I got rid of it)

Dennis

 

[glennc]

glennc,

On two of my computers on which I had those installations, I originally deleted the two executable(s). Then SFC complained and I did a System Restore and Disabled the two listed Services. All is well for about a week.

I did not want the chance that they would somehow "self-activate" and continue to monitor my keystrokes and other activity again. It is interesting that MS let this error continue without a fix since about June 6th. It almost seems like it was an alert to the knowing w/o admission of culpability.

BTW, I am still bugged about that "fix" link.

Dennis

Hey Dennis,
I PM'ed the Admin about that hyperlink issue, just in case!! Since this seems to be an update issue I started a thread about my issue there, along with your seemingly successful solution. Thanks again. As I do not have the knowledge, I am concerned and have not as yet disabled the suggested two services. I did stop them and after a reboot, even though set as "MANUAL", the first one of the two had restarted............
I am also have spent a lot of effort thinking that it was the latest update that caused the problem. Was the June 6th update a big one. I usually backup after each large update and the external drive only failed after the last update!!! Grrrrrrr.
glennc

 

[DennisCPA]

You may wish to Google/Bing those KB's and read about their background, you will be surprised.

I have changed my Window's Update settings from Automatic to just Alert. I now read the essence of the "more information" link on each and every KB before installing.

Note: I believe that Windows 10 will have diagtrackrunner.exe enabled.

 

[glennc]

Will do! It seems so counter-intuitive to have to check Microsoft updates before downloading them. Dropped the ball IMHO!
Take care!
glennc

 

[glennc]

Hello DennisCPA,
Your help seems to have succeeded in doing the trick! Running several days and no issues as well as a clean sfc /scannow Scan. Thank you for the assistance.
glennc

 

[glnz]

DennisCPA - thanks for your very helpful posts, here and elsewhere.

Something interesting: From your posts and others', I uninstalled many of the offending KBs and disabled your two services and finally got clean sfc /scannows, but found I still had diagtrackrunner.exe ONCE ONLY in my c:/ drive.

By mistake I tried to run it, but it didn't run and gave me the (happy) error message that it can't run because diagtrack.dll is missing. Good!

Now, I didn't delete diagtrack.dll and don't know why it's missing, but maybe everyone should delete diagtrack.dll, to stop diagtrackrunner.exe from running.

Worth a try?