Main Forum > Tweaking.com Support & Help

update history gone on Windows 10

<< < (2/7) > >>

hdrabkin:
Here is a follow-up: I was just notified that an update has been scheduled and will install on next reboot (Cumulative Update for Windows 10 Version 1511 for x64-based Systems (KB3163018)), so the reason for the original post is now moot (assuming the update installs ok and doesn't break anything else

Boggin:
After the update, run another sfc /scannow to see if it still reports problems.

DISM and CBS logs can be quite large and make difficult reading at the best of times.

To read a cut down version of the CBS log where it just shows what has and hasn't been repaired, enter this elevated cmd -

findstr /c:"[SR]" %windir%\Logs\CBS\CBS.log >"%userprofile%\Desktop\sfcdetails.txt

This will put an icon onto the desktop which when double clicked will open the CBS log in Notepad.

To get an even more concise report, run SFCFix.exe which can in some cases repair what a sfc /scannow can't.

http://www.majorgeeks.com/files/details/sfcfix.html

This can only be run after a sfc /scannow as it needs something to work on.

hdrabkin:
Sorry it's taken a while to get back to  you. Had to focus last week on work related issues.
So, interesting
Ran the scannow as suggested. There were some different issues that were not there before the most recent window update
Specifically, in the CBS log of 6/17, I see lines that say:
Error - Overlap: Duplicate ownership for directory [l:23]"\??\C:\WINDOWS\bcastdvr" in component Microsoft-Media-Capture-Internal-BroadcastDVR, version 10.0.10586.420, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
or
2016-06-17 21:17:17, Info                  CSI    00001326 [DIRSD OWNER WARNING] Directory [l:38 ml:39]"\??\C:\WINDOWS\System32\IME\shared\res" is not owned but specifies SDDL in component Microsoft-Windows-Desktop_Technologies-Text_Input_Services-IME-EAShared-IMEPad, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}
or
2016-06-17 21:17:18, Info                  CSI    0000134e [DIRSD OWNER WARNING] Directory [l:36 ml:37]"\??\C:\WINDOWS\System32\WDI\LogFiles" is not owned but specifies SDDL in component Microsoft-Windows-DiagnosticInfrastructure-Server, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

2016-06-17 21:17:18, Info                  CSI    0000134f [DIRSD OWNER WARNING] Directory [l:27 ml:28]"\??\C:\WINDOWS\System32\WDI" is not owned but specifies SDDL in component Microsoft-Windows-DiagnosticInfrastructure-Server, arch amd64, nonSxS, pkt {l:8 b:31bf3856ad364e35}

These types of errors were not in the 6/15 CBS.log created prior to the update!

Many like this. Interestingly, these are filtered out in sfcdetails.txt after running the command you suggested.

All of these "Duplicate ownership for directory" lines after the window update give me the feeling that an update was what started this whole mess  (the need to use Tweak to fix permissions,  etc.

When I ran the  SFCFix.exe , it give a log file of short length
AutoAnalysis::
SUMMARY: No corruptions were detected.
AutoAnalysis:: directive completed successfully.
Successfully processed all directives.
SFCFix version 3.0.0.0 by niemiro has completed.
Currently storing 0 datablocks.
Finish time: 2016-06-17 21:54:57.924

BUT while watching the screen in the background, I saw a typical DISM run that indicated that it could not find the files needed. These issues were not written to SFCFIX.text

I cannot use the command to give a filtered DISM; just gives an empty dismdetails.txt

Boggin:
Willy2 posted about the opencl.dll error back in March and then it was down to the November Update - http://news.softpedia.com/news/microsoft-acknowledges-system-file-checker-issue-in-windows-10-version-1511-502258.shtml

I don't know if it is related to the dual ownership though.

I'll see if I can get Shane (very busy) or Julian to have a look at it for you.

If you decide to run the Permissions reset in WR, ensure you manually create a registry backup in the program before proceeding, as it hasn't been auto creating one like it's supposed to.

Boggin:
MS has brought out this fix which may sort your problems - http://www.majorgeeks.com/files/details/microsofts_start_menu_troubleshooter.html

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version