Troubleshoot I dun goofed: System restore does not run through and I have issues with settings I made using W10Privacy and others

NulFunction

Level 2
Thread author
Verified
Jun 2, 2018
96
Briefly explain your current issue(s)
See OP
Steps taken to resolve, but have been unsuccessful
System restore, SFC, DISM. They all don't work
Hi

I recently used several privacy enhancing programs. Now I found some issues with these changes so wanted to turn back to default. I tried the restore point I made before setting em, but the restore process always ends in a message that it failed after reboot. (Even tried to restore from safe mode)
So I looked in the program and tried using the backups of the settings they first discovered. Unfortunately they are overwritten with my current setup FOR GOD KNOWS WHY! Even the change date is still the old one.

I guess that, from these three programs, it was W10Privacy who #####ed something up. (Others were O&O ShutUp and windows privacy tweaker)
Now I could go through it deactivate the culprit, but that is no solution because:
- Which setting did interfere with proper execution of system restore?
- Which setting does stop two specific links on my desktop to not use their icons anymore?
- Which setting does stop the Store application from reinstalling sticky notes? (It's not the obvious one! Reinstalling with it does not work)
- Which setting does stop the download of windows updates? (They stop at "Pending download")
- Which setting prohibits the dimming of my screen? (Laptop, via FN key.)

None of these issues are things that I can set.
I don't want to make a reset again. :(

Thank you!
 

NulFunction

Level 2
Thread author
Verified
Jun 2, 2018
96
That would have been a very easy solution, but no. My believes are that they harm more than they do good.

EDIT: I just accidentally read that "dism /Online /Cleanup-Image /RestoreHealth" reverts many changes made to settings, windows bloatware and whatnot. I'll try that.

EDIT:
Oh, for [moderated] sake!
Error: 0x800f0950
DISM failed. No operation was performed.
2018-06-06 01:22:44, Info DISM DISM Package Manager: PID=2860 TID=5304 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::private_ValidateCmdLine
2018-06-06 01:22:44, Info DISM DISM Package Manager: PID=2860 TID=5304 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2018-06-06 01:22:44, Info DISM DISM Package Manager: PID=2860 TID=5304 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2018-06-06 01:22:44, Info DISM DISM Package Manager: PID=2860 TID=5304 CBS session options=0x40100! - CDISMPackageManager::Internal_Finalize
2018-06-06 01:28:20, Info DISM DISM Package Manager: PID=2860 TID=5196 Error in operation: (null) (CBS HRESULT=0x800f0950) - CCbsConUIHandler::Error
2018-06-06 01:28:20, Error DISM DISM Package Manager: PID=2860 TID=5304 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0950)
2018-06-06 01:28:20, Error DISM DISM Package Manager: PID=2860 TID=5304 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f0950)
2018-06-06 01:28:20, Error DISM DISM Package Manager: PID=2860 TID=5304 Failed to restore the image health. - CPackageManagerCLIHandler::processCmdLine_CleanupImage(hr:0x800f0950)
2018-06-06 01:28:20, Error DISM DISM Package Manager: PID=2860 TID=5304 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0950)
2018-06-06 01:28:20, Info DISM DISM Package Manager: PID=2860 TID=5304 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2018-06-06 01:28:20, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F0950
...
2018-06-06 01:28:22, Info DISM DISM Package Manager: PID=8820 TID=8316 Processing the top level command token(cleanup-image). - CPackageManagerCLIHandler::private_ValidateCmdLine
2018-06-06 01:28:22, Info DISM DISM Package Manager: PID=8820 TID=8316 Attempting to route to appropriate command handler. - CPackageManagerCLIHandler::ExecuteCmdLine
2018-06-06 01:28:22, Info DISM DISM Package Manager: PID=8820 TID=8316 Routing the command... - CPackageManagerCLIHandler::ExecuteCmdLine
2018-06-06 01:28:22, Info DISM DISM Package Manager: PID=8820 TID=8316 CBS session options=0x40100! - CDISMPackageManager::Internal_Finalize
2018-06-06 01:37:20, Info DISM DISM Package Manager: PID=8820 TID=5396 Error in operation: (null) (CBS HRESULT=0x800f0950) - CCbsConUIHandler::Error
2018-06-06 01:37:20, Error DISM DISM Package Manager: PID=8820 TID=8316 Failed finalizing changes. - CDISMPackageManager::Internal_Finalize(hr:0x800f0950)
2018-06-06 01:37:20, Error DISM DISM Package Manager: PID=8820 TID=8316 Failed processing package changes with session option CbsSessionOptionRepairStoreCorruption - CDISMPackageManager::RestoreHealth(hr:0x800f0950)
2018-06-06 01:37:20, Error DISM DISM Package Manager: PID=8820 TID=8316 Failed to restore the image health. - CPackageManagerCLIHandler::processCmdLine_CleanupImage(hr:0x800f0950)
2018-06-06 01:37:20, Error DISM DISM Package Manager: PID=8820 TID=8316 Failed while processing command cleanup-image. - CPackageManagerCLIHandler::ExecuteCmdLine(hr:0x800f0950)
2018-06-06 01:37:20, Info DISM DISM Package Manager: PID=8820 TID=8316 Further logs for online package and feature related operations can be found at %WINDIR%\logs\CBS\cbs.log - CPackageManagerCLIHandler::ExecuteCmdLine
2018-06-06 01:37:20, Error DISM DISM.EXE: DISM Package Manager processed the command line but failed. HRESULT=800F0950
Why did it do that twice, btw?

2018-06-06 01:14:21, Info CBS TI: --- Initializing Trusted Installer ---
2018-06-06 01:14:21, Info CBS TI: Last boot time: 2018-06-05 23:19:33.486
2018-06-06 01:14:21, Info CBS Starting TrustedInstaller initialization.
2018-06-06 01:14:21, Info CBS Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:4
2018-06-06 01:14:21, Info CBS Lock: New lock added: CCbsPublicSessionClassFactory, level: 30, total lock:5
2018-06-06 01:14:21, Info CBS Lock: New lock added: WinlogonNotifyLock, level: 8, total lock:6
2018-06-06 01:14:21, Info CBS Ending TrustedInstaller initialization.
2018-06-06 01:14:21, Info CBS Starting the TrustedInstaller main loop.
2018-06-06 01:14:21, Info CBS TrustedInstaller service starts successfully.
2018-06-06 01:14:21, Info CBS No startup processing required, TrustedInstaller service was not set as autostart
2018-06-06 01:14:21, Info CBS Startup processing thread terminated normally
2018-06-06 01:14:21, Info CBS TI: Startup Processing completes, release startup processing lock.
2018-06-06 01:14:22, Info CBS Starting TiWorker initialization.
2018-06-06 01:14:22, Info CBS Lock: New lock added: TiWorkerClassFactory, level: 30, total lock:2
2018-06-06 01:14:22, Info CBS Ending TiWorker initialization.
2018-06-06 01:14:22, Info CBS Starting the TiWorker main loop.
2018-06-06 01:14:22, Info CBS TiWorker starts successfully.
2018-06-06 01:14:22, Info CBS Lock: New lock added: CCbsWorker, level: 5, total lock:3
2018-06-06 01:14:22, Info CBS Universal Time is: 2018-06-05 23:14:22.150
2018-06-06 01:14:22, Info CBS Loaded Servicing Stack v10.0.17134.1 with Core: C:\WINDOWS\winsxs\amd64_microsoft-windows-servicingstack_31bf3856ad364e35_10.0.17134.1_none_eedfeda03074e04e\cbscore.dll
2018-06-06 01:14:22, Info CBS Build: 17134.1.amd64fre.rs4_release.180410-1804
2018-06-06 01:14:22, Info CSI 00000001@2018/6/5:23:14:22.153 WcpInitialize (wcp.dll version 0.0.0.6) called (stack @0x7ffd03b2c2b9 @0x7ffd03e92a06 @0x7ffd03eadf1f @0x7ff6c7692c32 @0x7ff6c76935e8 @0x7ffd307d4bf3)
2018-06-06 01:14:22, Info CBS Lock: New lock added: CCbsSessionManager, level: 11, total lock:8
2018-06-06 01:14:22, Info CBS Lock: New lock added: CSIInventoryCriticalSection, level: 64, total lock:9
2018-06-06 01:14:22, Info CBS NonStart: Set pending store consistency check.
2018-06-06 01:14:22, Info CBS Session: 30670114_4027245362 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null
2018-06-06 01:14:22, Info CBS Client specifies manual store corruption detect or repair.
2018-06-06 01:14:22, Info CBS Exec: Session processing started. Client: Manual, Session(DISM Package Manager Provider Store Corruption Detect/Repair): 30670114_4027245362
2018-06-06 01:14:22, Info CBS Reboot mark set
2018-06-06 01:14:22, Info CBS Winlogon: Registering for CreateSession notifications
2018-06-06 01:14:22, Info CBS Winlogon: Loading SysNotify DLL
2018-06-06 01:14:22, Info CBS Winlogon: Starting notify server
2018-06-06 01:14:22, Info CBS FLOW: Entering stage: CheckCbs
2018-06-06 01:14:40, Info CBS Repr: CBS Store check completes
2018-06-06 01:14:40, Info CSI 00000002 IAdvancedInstallerAwareStore_ResolvePendingTransactions (call 1) (flags = 00000004, progress = NULL, phase = 0, pdwDisposition = @0x776f67d4d0
2018-06-06 01:14:40, Info CSI 00000003 Poqexec successfully registered in [l:12 ml:13]'SetupExecute'
2018-06-06 01:14:40, Info CSI 00000004 CSI Store 1864190514688 initialized
2018-06-06 01:14:40, Info CSI 00000005 StoreCorruptionRepair transaction begun. WcpVersion: [l:35]'10.0.17134.1 (WinBuild.160101.0800)'.
2018-06-06 01:14:40, Info CSI 00000006@2018/6/5:23:14:40.272 Starting corruption detection (InnerFlags=2)
2018-06-06 01:14:40, Info CBS FLOW: Entering stage: CheckCsi
2018-06-06 01:19:14, Info CSI 00000007 Hashes for file member [l:18]'Task Scheduler.lnk' do not match.
Expected: {l:32 ml:4096 b:0e6de115a6e3e83b616654ac65f87cc16ba13856b101082344bff665bd42821b}.
Actual: {l:32 b:89bceb4e95a052b0850c2303bdd79f445a6277c0c468c220fa20994a4a5dcbfb}.
2018-06-06 01:20:02, Info CBS Session: 30670115_3130960324 initialized by client LanguageSettings, external staging directory: (null), external registry directory: (null
2018-06-06 01:20:02, Info CBS Appl:Feature On Demand package without explicit comparator, using GE on build version
2018-06-06 01:20:02, Info CBS Appl:Feature On Demand package without explicit comparator, using GE on build version
2018-06-06 01:21:07, Warning CBS Current tick count: 1000 lower than last tick count: 1244. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2018-06-06 01:21:07, Error CSI 00000008@2018/6/5:23:21:07.055 (F) Attempting to mark store corrupt with category [l:18 ml:19]'CorruptPayloadFile'[gle=0x80004005]
2018-06-06 01:21:07, Info CSI 00000009@2018/6/5:23:21:07.107 Corruption detection complete. numCorruptions = 1, Disp = 1.
2018-06-06 01:21:07, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2018-06-06 01:21:07, Info CSI 0000000a@2018/6/5:23:21:07.176 CSI Transaction @0x1b20b201cf0 initialized for deployment engine {d16d444c-56d8-11d5-882d-0080c847b195} with flags 00000000 and client id 'TI5.30670114_4027245362:1/'

2018-06-06 01:21:07, Info CSI 0000000b@2018/6/5:23:21:07.181 CSI Transaction @0x1b20b201cf0 destroyed
2018-06-06 01:21:07, Info CBS Repr: CSI Store check completes
2018-06-06 01:21:07, Info CBS
2018-06-06 01:21:07, Info CBS =================================
2018-06-06 01:21:07, Info CBS Checking System Update Readiness.
2018-06-06 01:21:07, Info CBS
2018-06-06 01:21:07, Info CBS (p) CSI Payload Corrupt (n) amd64_taskschedulersettings_31bf3856ad364e35_10.0.17134.1_none_306b90216d874a70\Task Scheduler.lnk
2018-06-06 01:21:07, Info CBS
2018-06-06 01:21:07, Info CBS Summary:
2018-06-06 01:21:07, Info CBS Operation: Detect only
2018-06-06 01:21:07, Info CBS Operation result: 0x0
2018-06-06 01:21:07, Info CBS Last Successful Step: CSI store detection completes.
2018-06-06 01:21:07, Info CBS Total Detected Corruption: 1
2018-06-06 01:21:07, Info CBS CBS Manifest Corruption: 0
2018-06-06 01:21:07, Info CBS CBS Metadata Corruption: 0
2018-06-06 01:21:07, Info CBS CSI Manifest Corruption: 0
2018-06-06 01:21:07, Info CBS CSI Metadata Corruption: 0
2018-06-06 01:21:07, Info CBS CSI Payload Corruption: 1
2018-06-06 01:21:07, Info CBS Total Repaired Corruption: 0
2018-06-06 01:21:07, Info CBS CBS Manifest Repaired: 0
2018-06-06 01:21:07, Info CBS CSI Manifest Repaired: 0
2018-06-06 01:21:07, Info CBS CSI Payload Repaired: 0
2018-06-06 01:21:07, Info CBS CSI Store Metadata refreshed: True
2018-06-06 01:21:07, Info CBS
2018-06-06 01:21:07, Info CBS Total Operation Time: 404 seconds.
2018-06-06 01:21:07, Info CBS Ensure CBS corruption flag is clear
2018-06-06 01:21:07, Info CBS Not all CSI corruption was fixed, create CorruptionDetectedDuringAcr flag for slow mode reset
2018-06-06 01:21:07, Info CBS CheckSur: hrStatus: 0x0 [S_OK], download Result: 0x0 [S_OK]
2018-06-06 01:21:07, Info CBS Count of times corruption detected: 1
2018-06-06 01:21:07, Info CBS Failed to delete current corruption first found value. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2018-06-06 01:21:07, Info CBS Failed getting last corruption first found time [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2018-06-06 01:21:07, Info CBS Seconds between initial corruption detections: -1
2018-06-06 01:21:07, Info CBS Seconds between corruption and repair: -1
2018-06-06 01:21:07, Info CBS Reboot mark cleared
2018-06-06 01:21:07, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications
2018-06-06 01:21:07, Info CBS Winlogon: Deregistering for CreateSession notifications
2018-06-06 01:21:07, Info CBS Exec: Processing complete, session(Corruption Detecting): 30670114_4027245362 [HRESULT = 0x00000000 - S_OK]
2018-06-06 01:21:07, Info CBS Session: 30670114_4027245362 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
2018-06-06 01:21:07, Info CBS Session: 30670115_3784533777 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null
2018-06-06 01:22:44, Info CBS Session: 30670116_459711143 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null
2018-06-06 01:22:44, Info CBS Client specifies manual store corruption detect or repair.
2018-06-06 01:22:44, Info CBS Exec: Session processing started. Client: Manual, Session(DISM Package Manager Provider Store Corruption Detect/Repair): 30670116_459711143
2018-06-06 01:22:44, Info CBS Reboot mark set
2018-06-06 01:22:44, Info CBS Winlogon: Registering for CreateSession notifications
2018-06-06 01:22:44, Info CBS FLOW: Entering stage: CheckCbs
2018-06-06 01:23:03, Info CBS Repr: CBS Store check completes
2018-06-06 01:23:03, Info CSI 0000000c StoreCorruptionRepair transaction begun. WcpVersion: [l:35]'10.0.17134.1 (WinBuild.160101.0800)'.
2018-06-06 01:23:03, Info CSI 0000000d@2018/6/5:23:23:03.628 Starting corruption detection (InnerFlags=2)
2018-06-06 01:23:03, Info CBS FLOW: Entering stage: CheckCsi
2018-06-06 01:26:30, Info CSI 0000000e Hashes for file member [l:18]'Task Scheduler.lnk' do not match.
Expected: {l:32 ml:4096 b:0e6de115a6e3e83b616654ac65f87cc16ba13856b101082344bff665bd42821b}.
Actual: {l:32 b:89bceb4e95a052b0850c2303bdd79f445a6277c0c468c220fa20994a4a5dcbfb}.
2018-06-06 01:28:18, Warning CBS Current tick count: 800 lower than last tick count: 992. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2018-06-06 01:28:18, Error CSI 0000000f@2018/6/5:23:28:18.463 (F) Attempting to mark store corrupt with category [l:18 ml:19]'CorruptPayloadFile'[gle=0x80004005]
2018-06-06 01:28:18, Info CSI 00000010@2018/6/5:23:28:18.545 Corruption detection complete. numCorruptions = 1, Disp = 1.
2018-06-06 01:28:18, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2018-06-06 01:28:18, Info CBS Repr: CSI Store check completes
2018-06-06 01:28:18, Info CBS Exec: Download qualification evaluation, business scenario: Manual Corruption Repair
2018-06-06 01:28:18, Info CBS Exec: Clients specified using Windows Update.
2018-06-06 01:28:18, Info CBS Repr: Add missing payload:amd64_taskschedulersettings_31bf3856ad364e35_10.0.17134.1_none_306b90216d874a70\Task Scheduler.lnk
2018-06-06 01:28:18, Info CBS FC: Calling Download on WUClient Acquirer
2018-06-06 01:28:18, Info CBS FC: Calling WindowsUpdateDownloadFromUUP
2018-06-06 01:28:18, Info CBS FC: WULib Mode Complete: [0]
2018-06-06 01:28:18, Info CBS WU: Microsoft Update service is the default, URL: https://fe2.update.microsoft.com/v6/, Name: Microsoft Update
2018-06-06 01:28:18, Info CBS Not able to read BranchName [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-06-06 01:28:18, Info CBS Not able to read ContentType [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-06-06 01:28:18, Info CBS Not able to read Ring [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-06-06 01:28:18, Info CBS Not able to read IsBuildFlightingEnabled [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-06-06 01:28:18, Info CBS Windows Insider Program: Current settings: Content type: (null), Build branch: (null), Ring: (null), Build Flighting Enabled: No
2018-06-06 01:28:18, Info CBS WU: Windows update server selection group policy not set [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-06-06 01:28:18, Info CBS DWLD: Current product search criteria: (Product='Client.OS.rs2.amd64' and CurrentVersionOnly=1)
2018-06-06 01:28:20, Info CBS DLWD: Expecting search returns 1 update, actual:0 [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:28:20, Info CBS DWLD:Failed to do Windows update search [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:28:20, Info CBS FC: WindowsUpdateDownloadFromUUP returns. [0x800F0950]
2018-06-06 01:28:20, Error CBS FC: CFCAcquirerWUClient::Download(136): Result = 0x800F0950
2018-06-06 01:28:20, Error CBS FC: CFCAcquirerWrapper::Execute(147): Result = 0x800F0950
2018-06-06 01:28:20, Info CBS Failed to enumerate online uup features [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:28:20, Info CBS Failed to download missing files [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:28:20, Info CBS Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:28:20, Info CBS Failed to repair store. [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:28:20, Info CBS
2018-06-06 01:28:20, Info CBS =================================
2018-06-06 01:28:20, Info CBS Checking System Update Readiness.
2018-06-06 01:28:20, Info CBS
2018-06-06 01:28:20, Info CBS (p) CSI Payload Corrupt (n) amd64_taskschedulersettings_31bf3856ad364e35_10.0.17134.1_none_306b90216d874a70\Task Scheduler.lnk
2018-06-06 01:28:20, Info CBS Repair failed: Missing replacement payload.
2018-06-06 01:28:20, Info CBS
2018-06-06 01:28:20, Info CBS Summary:
2018-06-06 01:28:20, Info CBS Operation: Detect and Repair
2018-06-06 01:28:20, Info CBS Operation result: 0x800f0950
2018-06-06 01:28:20, Info CBS Last Successful Step: Entire operation completes.
2018-06-06 01:28:20, Info CBS Total Detected Corruption: 1
2018-06-06 01:28:20, Info CBS CBS Manifest Corruption: 0
2018-06-06 01:28:20, Info CBS CBS Metadata Corruption: 0
2018-06-06 01:28:20, Info CBS CSI Manifest Corruption: 0
2018-06-06 01:28:20, Info CBS CSI Metadata Corruption: 0
2018-06-06 01:28:20, Info CBS CSI Payload Corruption: 1
2018-06-06 01:28:20, Info CBS Total Repaired Corruption: 0
2018-06-06 01:28:20, Info CBS CBS Manifest Repaired: 0
2018-06-06 01:28:20, Info CBS CSI Manifest Repaired: 0
2018-06-06 01:28:20, Info CBS CSI Payload Repaired: 0
2018-06-06 01:28:20, Info CBS CSI Store Metadata refreshed: True
2018-06-06 01:28:20, Info CBS
2018-06-06 01:28:20, Info CBS Total Operation Time: 335 seconds.
2018-06-06 01:28:20, Info CBS Ensure CBS corruption flag is clear
2018-06-06 01:28:20, Info CBS Not all CSI corruption was fixed, create CorruptionDetectedDuringAcr flag for slow mode reset
2018-06-06 01:28:20, Info CBS CheckSur: hrStatus: 0x800f0950 [CBS_E_INVALID_WINDOWS_UPDATE_COUNT], download Result: 0x0 [S_OK]
2018-06-06 01:28:20, Info CBS Count of times corruption detected: 1
2018-06-06 01:28:20, Info CBS Seconds between initial corruption detections: -1
2018-06-06 01:28:20, Info CBS Seconds between corruption and repair: -1
2018-06-06 01:28:20, Info CBS Failed to run Detect and repair. [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:28:20, Info CBS Reboot mark cleared
2018-06-06 01:28:20, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications
2018-06-06 01:28:20, Info CBS Winlogon: Deregistering for CreateSession notifications
2018-06-06 01:28:20, Info CBS Exec: Processing complete, session(Corruption Repairing): 30670116_459711143 [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:28:20, Error CBS Session: 30670116_459711143 failed to perform store corruption detect and repair operation. [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:28:20, Info CBS Session: 30670116_459711143 finalized. Reboot required: no [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:28:20, Info CBS Failed to FinalizeEx using worker session [HRESULT = 0x800f0950]
2018-06-06 01:28:22, Info CBS Session: 30670116_3839060689 initialized by client DISM Package Manager Provider, external staging directory: (null), external registry directory: (null
2018-06-06 01:28:22, Info CBS Client specifies manual store corruption detect or repair.
2018-06-06 01:28:22, Info CBS Exec: Session processing started. Client: Manual, Session(DISM Package Manager Provider Store Corruption Detect/Repair): 30670116_3839060689
2018-06-06 01:28:22, Info CBS Reboot mark set
2018-06-06 01:28:22, Info CBS Winlogon: Registering for CreateSession notifications
2018-06-06 01:28:22, Info CBS FLOW: Entering stage: CheckCbs
2018-06-06 01:28:58, Info CBS Repr: CBS Store check completes
2018-06-06 01:28:58, Info CSI 00000011 StoreCorruptionRepair transaction begun. WcpVersion: [l:35]'10.0.17134.1 (WinBuild.160101.0800)'.
2018-06-06 01:28:58, Info CSI 00000012@2018/6/5:23:28:58.972 Starting corruption detection (InnerFlags=2)
2018-06-06 01:28:58, Info CBS FLOW: Entering stage: CheckCsi
2018-06-06 01:35:10, Info CSI 00000013 Hashes for file member [l:18]'Task Scheduler.lnk' do not match.
Expected: {l:32 ml:4096 b:0e6de115a6e3e83b616654ac65f87cc16ba13856b101082344bff665bd42821b}.
Actual: {l:32 b:89bceb4e95a052b0850c2303bdd79f445a6277c0c468c220fa20994a4a5dcbfb}.
2018-06-06 01:37:18, Warning CBS Current tick count: 800 lower than last tick count: 992. [HRESULT = 0x8007000d - ERROR_INVALID_DATA]
2018-06-06 01:37:18, Error CSI 00000014@2018/6/5:23:37:18.925 (F) Attempting to mark store corrupt with category [l:18 ml:19]'CorruptPayloadFile'[gle=0x80004005]
2018-06-06 01:37:18, Info CSI 00000015@2018/6/5:23:37:18.995 Corruption detection complete. numCorruptions = 1, Disp = 1.
2018-06-06 01:37:19, Info CBS Repr: CSI meta data corruption found, will commit repair transaction if repair is asked.
2018-06-06 01:37:19, Info CBS Repr: CSI Store check completes
2018-06-06 01:37:19, Info CBS Exec: Download qualification evaluation, business scenario: Manual Corruption Repair
2018-06-06 01:37:19, Info CBS Exec: Clients specified using Windows Update.
2018-06-06 01:37:19, Info CBS Repr: Add missing payload:amd64_taskschedulersettings_31bf3856ad364e35_10.0.17134.1_none_306b90216d874a70\Task Scheduler.lnk
2018-06-06 01:37:19, Info CBS FC: Calling Download on WUClient Acquirer
2018-06-06 01:37:19, Info CBS FC: Calling WindowsUpdateDownloadFromUUP
2018-06-06 01:37:19, Info CBS FC: WULib Mode Complete: [0]
2018-06-06 01:37:19, Info CBS WU: Microsoft Update service is the default, URL: https://fe2.update.microsoft.com/v6/, Name: Microsoft Update
2018-06-06 01:37:19, Info CBS Not able to read BranchName [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-06-06 01:37:19, Info CBS Not able to read ContentType [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-06-06 01:37:19, Info CBS Not able to read Ring [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-06-06 01:37:19, Info CBS Not able to read IsBuildFlightingEnabled [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-06-06 01:37:19, Info CBS Windows Insider Program: Current settings: Content type: (null), Build branch: (null), Ring: (null), Build Flighting Enabled: No
2018-06-06 01:37:19, Info CBS WU: Windows update server selection group policy not set [HRESULT = 0x80070002 - ERROR_FILE_NOT_FOUND]
2018-06-06 01:37:19, Info CBS DWLD: Current product search criteria: (Product='Client.OS.rs2.amd64' and CurrentVersionOnly=1)
2018-06-06 01:37:20, Info CBS DLWD: Expecting search returns 1 update, actual:0 [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:37:20, Info CBS DWLD:Failed to do Windows update search [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:37:20, Info CBS FC: WindowsUpdateDownloadFromUUP returns. [0x800F0950]
2018-06-06 01:37:20, Error CBS FC: CFCAcquirerWUClient::Download(136): Result = 0x800F0950
2018-06-06 01:37:20, Error CBS FC: CFCAcquirerWrapper::Execute(147): Result = 0x800F0950
2018-06-06 01:37:20, Info CBS Failed to enumerate online uup features [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:37:20, Info CBS Failed to download missing files [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:37:20, Info CBS Failed to collect payload and there is nothing to repair. [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:37:20, Info CBS Failed to repair store. [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:37:20, Info CBS
2018-06-06 01:37:20, Info CBS =================================
2018-06-06 01:37:20, Info CBS Checking System Update Readiness.
2018-06-06 01:37:20, Info CBS
2018-06-06 01:37:20, Info CBS (p) CSI Payload Corrupt (n) amd64_taskschedulersettings_31bf3856ad364e35_10.0.17134.1_none_306b90216d874a70\Task Scheduler.lnk
2018-06-06 01:37:20, Info CBS Repair failed: Missing replacement payload.
2018-06-06 01:37:20, Info CBS
2018-06-06 01:37:20, Info CBS Summary:
2018-06-06 01:37:20, Info CBS Operation: Detect and Repair
2018-06-06 01:37:20, Info CBS Operation result: 0x800f0950
2018-06-06 01:37:20, Info CBS Last Successful Step: Entire operation completes.
2018-06-06 01:37:20, Info CBS Total Detected Corruption: 1
2018-06-06 01:37:20, Info CBS CBS Manifest Corruption: 0
2018-06-06 01:37:20, Info CBS CBS Metadata Corruption: 0
2018-06-06 01:37:20, Info CBS CSI Manifest Corruption: 0
2018-06-06 01:37:20, Info CBS CSI Metadata Corruption: 0
2018-06-06 01:37:20, Info CBS CSI Payload Corruption: 1
2018-06-06 01:37:20, Info CBS Total Repaired Corruption: 0
2018-06-06 01:37:20, Info CBS CBS Manifest Repaired: 0
2018-06-06 01:37:20, Info CBS CSI Manifest Repaired: 0
2018-06-06 01:37:20, Info CBS CSI Payload Repaired: 0
2018-06-06 01:37:20, Info CBS CSI Store Metadata refreshed: True
2018-06-06 01:37:20, Info CBS
2018-06-06 01:37:20, Info CBS Total Operation Time: 537 seconds.
2018-06-06 01:37:20, Info CBS Ensure CBS corruption flag is clear
2018-06-06 01:37:20, Info CBS Not all CSI corruption was fixed, create CorruptionDetectedDuringAcr flag for slow mode reset
2018-06-06 01:37:20, Info CBS CheckSur: hrStatus: 0x800f0950 [CBS_E_INVALID_WINDOWS_UPDATE_COUNT], download Result: 0x0 [S_OK]
2018-06-06 01:37:20, Info CBS Count of times corruption detected: 1
2018-06-06 01:37:20, Info CBS Seconds between initial corruption detections: -1
2018-06-06 01:37:20, Info CBS Seconds between corruption and repair: -1
2018-06-06 01:37:20, Info CBS Failed to run Detect and repair. [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:37:20, Info CBS Reboot mark cleared
2018-06-06 01:37:20, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications
2018-06-06 01:37:20, Info CBS Winlogon: Deregistering for CreateSession notifications
2018-06-06 01:37:20, Info CBS Exec: Processing complete, session(Corruption Repairing): 30670116_3839060689 [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:37:20, Error CBS Session: 30670116_3839060689 failed to perform store corruption detect and repair operation. [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:37:20, Info CBS Session: 30670116_3839060689 finalized. Reboot required: no [HRESULT = 0x800f0950 - CBS_E_INVALID_WINDOWS_UPDATE_COUNT]
2018-06-06 01:37:20, Info CBS Failed to FinalizeEx using worker session [HRESULT = 0x800f0950]
2018-06-06 01:39:20, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2018-06-06 01:39:20, Info CBS TiWorker signaled for shutdown, going to exit.
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2018-06-06 01:39:20, Info CBS Execution Engine Finalize
2018-06-06 01:39:20, Info CBS Execution Engine Finalize
2018-06-06 01:39:20, Info CBS Ending the TiWorker main loop.
2018-06-06 01:39:20, Info CBS Starting TiWorker finalization.
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: ManifestCacheFinalize
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2018-06-06 01:39:20, Info CBS CBS Engine already deativated
2018-06-06 01:39:20, Info CBS CBS Engine already deativated
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: ComponentAnalyzerFinalize
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: PackageTrackerFinalize
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: CoreResourcesUnload
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: SessionManagerFinalize
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: CapabilityManagerFinalize
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: PublicObjectMonitorFinalize
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: Enter vCoreInitializeLock
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: WcpUnload
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: DrupUnload
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: CfgMgr32Unload
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: DpxUnload
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: SrUnload
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: CbsEsdUnload
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: CbsTraceInfoUninitialize
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: CbsEventUnregister
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: AppContainerUnload
2018-06-06 01:39:20, Info CBS CbsCoreFinalize: WdsUnload, logging from cbscore will end.
2018-06-06 01:39:20, Info CBS Ending TiWorker finalization.
2018-06-06 01:39:20, Info CBS Ending the TrustedInstaller main loop.
2018-06-06 01:39:20, Info CBS Starting TrustedInstaller finalization.
2018-06-06 01:39:20, Info CBS Winlogon: Stopping notify server
2018-06-06 01:39:20, Info CBS Winlogon: Unloading SysNotify DLL
2018-06-06 01:39:20, Info CBS Ending TrustedInstaller finalization.

I am doing it again now with all protection programs disabled and SFC beforehand
EDIT: No.
 
Last edited by a moderator:
  • Like
Reactions: vtqhtr413
Upvote 0

SumTingWong

Level 28
Verified
Top Poster
Well-known
Apr 2, 2018
1,721
Argh ... please! :cry: I don't want to make another in-place upgrade again (Just installed 1803) and re-do all the settings I've done. :sick:

;):D Damn that easily breakable piece of f*ing porcelain figurine!

This is why you should have a backup image. Windows Restore Point is not reliable at all. You can buy a cheap 1TB portable drive use for backup with free backupper like AOMEI or Macrium Reflect.
 
Upvote 0
D

Deleted Member 3a5v73x

I always whenever new Windows upgrade comes out, save my documents and make a system image in MRF, create a USB with MediaCreationTool with newest Windows and do a basic installation without custom settings/programms and create another system image, then install all my daily needed software/set settings and create another image, then I'm all set.

I suggest you mate start everything from the beginning with clean install and learn the basics of Macrium Reflect Free, it will save you time in future and you will be grateful for doing that.

System restore points sometimes may become corrupted and you really shouldn't relay on them. I also in the past when changed gpedit/regedit/messed with O&O, WPD stuff forgot afterwards what settings I changed and Windows updates may disable some settings from time to time, so you have to re-do them and all that hassle. Save your nerves and either look at the Macrium Reflect Free or Aomei Backuper. Good luck. ;)
 
Last edited by a moderator:
Upvote 0

show-Zi

Level 36
Verified
Top Poster
Well-known
Jan 28, 2018
2,463
Try booting from another boot drive. So there are cases where restoration succeeds. It is also recommended to check the system file with sfc etc after the restoration is successful. In many cases the consistency is confused and the system is in an unstable state.

Although restoration is a convenient recovery method, I think that it is better to recognize it as an adhesive bandage degree. In my personal opinion, the restoration point is a consumption time limit of about six hours after creation.
Consider regularly backing up the system image. Here it is reliable as long-term use as frozen food as possible.
 
Upvote 0

Ink

Administrator
Verified
Staff Member
Well-known
Jan 8, 2011
22,361
System Restore is insufficient. If you cannot fix or repair the OS, try Reset this PC (Keep personal files).

1528285433359.png



Originally System Restore was disabled by default for Windows 10 RTM. Is this still the case for Windows 10 v1803, clean install?
 
Upvote 0
I

illumination

Hard lesson to learn messing with many 3rd party applications, that corrupted the system. At this point, you would be better off, using the media creation tool as you listed in your config, and wiping the system and performing a clean install.

Restore points "if you enable", images both external and built in can become corrupted as well, a fresh burn of W10 1803 to a flash drive, and verified files intact, will be your best bet.

In the future i would recommend not utilizing 3rd party applications to try and achieve the impossible. You can not have privacy now days without "you just experienced it", crippling your OS...
 
Upvote 0

NulFunction

Level 2
Thread author
Verified
Jun 2, 2018
96
Ok... I'm looking at Macrium Reflect Free. Does it work with an external HDD over USB? I guess you get a live CD which you boot from. (I only need to backup a maximum of 75% of my 150GB SSD space.)
But regular images? How do I know I am not infected at the time I make an image? I could back up rootkit malware and never get rid of it.
I guess that is paranoid.

EDIT: Seems like DISM or SFC repaired stuff. Windows Update does work now and at least one of the two missing icons on my desktop are back. XD How is that even possible?

EDIT: Oh yea, someone said to try DISM with a windows cd. Doing that now
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\sxs
edit.. nope. doesn't even start. I'll try to run some repair from the cd.
 
Last edited:
Upvote 0

SumTingWong

Level 28
Verified
Top Poster
Well-known
Apr 2, 2018
1,721
Ok... I'm looking at Macrium Reflect Free. Does it work with an external HDD over USB? I guess you get a live CD which you boot from. (I only need to backup a maximum of 75% of my 150GB SSD space.)
But regular images? How do I know I am not infected at the time I make an image? I could back up rootkit malware and never get rid of it.
I guess that is paranoid.

EDIT: Seems like DISM or SFC repaired stuff. Windows Update does work now and at least one of the two missing icons on my desktop are back. XD How is that even possible?

EDIT: Oh yea, someone said to try DISM with a windows cd. Doing that now
DISM.exe /Online /Cleanup-Image /RestoreHealth /Source:E:\sources\sxs
edit.. nope. doesn't even start. I'll try to run some repair from the cd.

It works with drives using USB 3.0 . If you are going to use Aomei free backupper, you can put a description under your backup. Make sure you run your antivirus scanner just to make sure it is virus free before doing an image backup. I don't know about Macrium Reflect because I haven't used it at all.
 
Upvote 0

NulFunction

Level 2
Thread author
Verified
Jun 2, 2018
96
Ok.
First I want to get rid of the last issue I have, afaik: Windows update stuck at "download pending" SOMETIMES ONLY

EDIT: Oops I forgot I have the diagcab for troubleshooting windows update. I've done that. Works.
 
Last edited:
  • Like
Reactions: vtqhtr413
Upvote 0

NulFunction

Level 2
Thread author
Verified
Jun 2, 2018
96
Yes, sry, that's what I meant with "works"
I may try to create a new system restore point and see if it can be restored...
then look if DISM works again and maybe I'll make an image of my installation afterwards. (DISM needs windows update, afaik)
 
  • Like
Reactions: vtqhtr413
Upvote 0

NulFunction

Level 2
Thread author
Verified
Jun 2, 2018
96
Unfortunately nothing has helped make DISM work again. I tried chkdsk at system boot, but that only got to 16% the last time I tried. I'll do that again next, but before I'm going in the W10Privacy app and uncheck almost everything.
 
Upvote 0

SumTingWong

Level 28
Verified
Top Poster
Well-known
Apr 2, 2018
1,721
Unfortunately nothing has helped make DISM work again. I tried chkdsk at system boot, but that only got to 16% the last time I tried. I'll do that again next, but before I'm going in the W10Privacy app and uncheck almost everything.

I think the more you try to fix your system at this current stage, the worse it will get. This is why you need an image backup in the first place, and not the Windows System Restore.
 
Upvote 0

About us

  • MalwareTips is a community-driven platform providing the latest information and resources on malware and cyber threats. Our team of experienced professionals and passionate volunteers work to keep the internet safe and secure. We provide accurate, up-to-date information and strive to build a strong and supportive community dedicated to cybersecurity.

User Menu

Follow us

Follow us on Facebook or Twitter to know first about the latest cybersecurity incidents and malware threats.

Top