Settings / Update & Security 화면 진입 시 프로그램 종료
윈도우 서버를 2016에서 2019로 업그레이드 후 Settings / "Update & Security" 화면으로 진입하면 그냥 프로그램이 꺼집니다. ^^; 이때의 이벤트 로그는 다음과 같이 남고,
Log Name: Application
Source: Windows Error Reporting
Date: 2019-07-15 오후 2:53:55
Event ID: 1001
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: testpc.testad.com
Description:
Fault bucket 1416711185245545695, type 5
Event Name: MoAppCrash
Response: Not available
Cab Id: 0
Problem signature:
P1: windows.immersivecontrolpanel_10.0.2.1000_neutral_neutral_cw5n1h2txyewy
P2: praid:microsoft.windows.immersivecontrolpanel
P3: 10.0.17763.1
P4: 9d9d9332
P5: MusUpdateHandlers.dll
P6: 10.0.17763.592
P7: 1ae87a6f
P8: c0000005
P9: 0000000000057684
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1A93.tmp.dmp
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E0F.tmp.WERInternalMetadata.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E4E.tmp.xml
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E4C.tmp.csv
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER1E7C.tmp.txt
These files may be available here:
\\?\C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_windows.immersiv_6826c810c2fc17e5d781a9fa3c39585def59c32e_31aeda3d_2713232e
Analysis symbol:
Rechecking for solution: 0
Report Id: a301e200-5896-49d9-bcd5-bf6911c47d1f
Report Status: 268435456
Hashed bucket: 6f6ac3e0870b0f9cc3a92b5121e224df
Cab Guid: 0
Log Name: Application
Source: Application Error
Date: 2019-07-15 오후 2:53:53
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: testpc.testad.com
Description:
Faulting application name: SystemSettings.exe, version: 10.0.17763.1, time stamp: 0x9d9d9332
Faulting module name: MusUpdateHandlers.dll, version: 10.0.17763.592, time stamp: 0x1ae87a6f
Exception code: 0xc0000005
Fault offset: 0x0000000000057684
Faulting process id: 0x1d34
Faulting application start time: 0x01d53ad1a9df725d
Faulting application path: C:\Windows\ImmersiveControlPanel\SystemSettings.exe
Faulting module path: C:\Windows\System32\MusUpdateHandlers.dll
Report Id: a301e200-5896-49d9-bcd5-bf6911c47d1f
Faulting package full name: windows.immersivecontrolpanel_10.0.2.1000_neutral_neutral_cw5n1h2txyewy
Faulting package-relative application ID: microsoft.windows.immersivecontrolpanel
검색해 보면,
Update & Security tab crashes
; https://www.tenforums.com/general-support/43985-update-security-tab-crashes.html
이렇게 해결책이 나옵니다.
sfc /scannow
> press Enter.
It will take quite sometime.
When finished, it will give you one of the 3 reports...............(paraphrasing)
1. No integrity violation.
2. Found corrupt files and repair successful.
3. Found corrupt files but unable to repair.
If the report is #1, your solution lies elsewhere.
If the report is #2, check if your problems have been resolved.
If the report is #3, use this method................
In the same Command Prompt (Admin) windows, copy and paste this command...........
dism /online /cleanup-image /restorehealth
이리저리 실행해 본 게 많아서 좀 혼란스러운데, ^^; 제 경우에는 /StartComponentCleanup 옵션 이후 정상적으로 Update 창이 유지된 것 같습니다. 따라서 다음과 같은 명령어들을 (오류가 발생해도) 그냥 수행을 하고 나면 Update 창이 사라지는 문제는 없어질 것입니다.
Dism.exe /online /Cleanup-Image /StartComponentCleanup
sfc /scannow
Dism /Online /Cleanup-Image /RestoreHealth
sfc /scannow
그런데 Update 창 문제는 사라졌지만, 제 경우에는 dism.exe와 sfc.exe 실행 시 여전히 다음과 같은 식의 오류가 발생했습니다.
PS C:\WINDOWS\system32> sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files but was unable to fix some of them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.
PS C:\WINDOWS\system32> dism /online /cleanup-image /restorehealth
Deployment Image Servicing and Management tool
Version: 10.0.17763.1
Image Version: 10.0.17763.615
[==========================100.0%==========================]
Error: 0x800f081f
The source files could not be found.
Use the "Source" option to specify the location of the files that are required to restore the feature. For more information on specifying a source location, see http://go.microsoft.com/fwlink/?LinkId=243077.
The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log
CBS.log 파일과 dism.log 파일을 분석해 보면, sfc.exe의 경우 내부적으로 dism.exe를 호출하게 되고 dism.exe 내부 작업 수행 시 오류가 발생한 것이므로 결국 문제는 sfc.exe가 아닌 dism.exe에 있는 경우였습니다. 따라서 dism.exe의 오류 로그가 중요한데 "Source" 옵션을 지정해 해결하라는 문구가 나옵니다. 실제로 로그 파일을 보면,
2019-07-17 12:22:41, Info CBS =================================
2019-07-17 12:22:41, Info CBS Checking System Update Readiness.
2019-07-17 12:22:41, Info CBS
2019-07-17 12:22:41, Info CBS (p) CSI Payload Corrupt (n) amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpComputerStatus.cdxml
2019-07-17 12:22:41, Info CBS Repair failed: Missing replacement payload.
2019-07-17 12:22:41, Info CBS (p) CSI Payload Corrupt (n) amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreat.cdxml
2019-07-17 12:22:41, Info CBS Repair failed: Missing replacement payload.
2019-07-17 12:22:41, Info CBS (p) CSI Payload Corrupt (n) amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreatCatalog.cdxml
2019-07-17 12:22:41, Info CBS Repair failed: Missing replacement payload.
2019-07-17 12:22:41, Info CBS (p) CSI Payload Corrupt (n) amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpThreatDetection.cdxml
2019-07-17 12:22:41, Info CBS Repair failed: Missing replacement payload.
2019-07-17 12:22:41, Info CBS (p) CSI Payload Corrupt (n) amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpPreference.cdxml
2019-07-17 12:22:41, Info CBS Repair failed: Missing replacement payload.
2019-07-17 12:22:41, Info CBS (p) CSI Payload Corrupt (n) amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpScan.cdxml
2019-07-17 12:22:41, Info CBS Repair failed: Missing replacement payload.
2019-07-17 12:22:41, Info CBS (p) CSI Payload Corrupt (n) amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpWDOScan.cdxml
2019-07-17 12:22:41, Info CBS Repair failed: Missing replacement payload.
2019-07-17 12:22:41, Info CBS (p) CSI Payload Corrupt (n) amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\MSFT_MpSignature.cdxml
2019-07-17 12:22:41, Info CBS Repair failed: Missing replacement payload.
2019-07-17 12:22:41, Info CBS (p) CSI Payload Corrupt (n) amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.17763.1_none_d48944eff97b9138\Defender.psd1
2019-07-17 12:22:41, Info CBS Repair failed: Missing replacement payload.
2019-07-17 12:22:41, Info CBS
2019-07-17 12:22:41, Info CBS Summary:
2019-07-17 12:22:41, Info CBS Operation: Detect and Repair
2019-07-17 12:22:41, Info CBS Operation result: 0x800f081f
2019-07-17 12:22:41, Info CBS Last Successful Step: Entire operation completes.
2019-07-17 12:22:41, Info CBS Total Detected Corruption: 9
2019-07-17 12:22:41, Info CBS CBS Manifest Corruption: 0
2019-07-17 12:22:41, Info CBS CBS Metadata Corruption: 0
2019-07-17 12:22:41, Info CBS CSI Manifest Corruption: 0
2019-07-17 12:22:41, Info CBS CSI Metadata Corruption: 0
2019-07-17 12:22:41, Info CBS CSI Payload Corruption: 9
2019-07-17 12:22:41, Info CBS Total Repaired Corruption: 0
2019-07-17 12:22:41, Info CBS CBS Manifest Repaired: 0
2019-07-17 12:22:41, Info CBS CSI Manifest Repaired: 0
2019-07-17 12:22:41, Info CBS CSI Payload Repaired: 0
2019-07-17 12:22:41, Info CBS CSI Store Metadata refreshed: True
2019-07-17 12:22:41, Info CBS
2019-07-17 12:22:41, Info CBS Total Operation Time: 1516 seconds.
2019-07-17 12:22:41, Info CBS Ensure CBS corruption flag is clear
2019-07-17 12:22:41, Info CBS Not all CSI corruption was fixed, create CorruptionDetectedDuringAcr flag for slow mode reset
2019-07-17 12:22:41, Info CBS CheckSur: hrStatus: 0x800f081f [CBS_E_SOURCE_MISSING], download Result: 0x800f081f [CBS_E_SOURCE_MISSING]
2019-07-17 12:22:41, Info CBS Count of times corruption detected: 1
2019-07-17 12:22:41, Info CBS Seconds between initial corruption detections: -1
2019-07-17 12:22:41, Info CBS Seconds between corruption and repair: -1
2019-07-17 12:22:41, Info CBS Failed to run Detect and repair. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2019-07-17 12:22:41, Info CBS Reboot mark cleared
2019-07-17 12:22:41, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications
2019-07-17 12:22:41, Info CBS Winlogon: Deregistering for CreateSession notifications
2019-07-17 12:22:41, Info CBS Exec: Processing complete, session(Corruption Repairing): 30751819_1548573486 [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2019-07-17 12:22:41, Error CBS Session: 30751819_1548573486 failed to perform store corruption detect and repair operation. [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2019-07-17 12:22:41, Info CBS Session: 30751819_1548573486 finalized. Reboot required: no [HRESULT = 0x800f081f - CBS_E_SOURCE_MISSING]
2019-07-17 12:22:41, Info CBS Failed to FinalizeEx using worker session [HRESULT = 0x800f081f]
2019-07-17 12:24:52, Info CBS Trusted Installer is shutting down because: SHUTDOWN_REASON_AUTOSTOP
2019-07-17 12:24:52, Info CBS TiWorker signaled for shutdown, going to exit.
2019-07-17 12:24:52, Info CBS CbsCoreFinalize: ExecutionEngineFinalize
2019-07-17 12:24:52, Info CBS Execution Engine Finalize
CSI Payload Corrupt, CBS_E_SOURCE_MISSING 등의 메시지가 나오는데 아마도 저 오류가 발생하는 파일들을 찾을 수 없다는 의미로 보입니다. 이에 대한 해결책은 다음의 글에서 찾을 수 있습니다.
How to fix DISM 0x800f081f Error in Windows 10/8 (Solved)
; https://www.wintips.org/fix-dism-0x800f081f-error-in-windows-10-8/
위의 글을 바탕으로, 제 경우에는 Windows Server 2019 Datacenter (Desktop Experience)로 업그레이드하려고 했기 때문에 해당 설치 디스크(ISO)의 install.wim 상태를 확인하고,
C:\WINDOWS\system32> dism /Get-WimInfo /WimFile:d:\sources\install.wim
Deployment Image Servicing and Management tool
Version: 10.0.17763.1
Details for image : d:\sources\install.wim
Index : 1
Name : Windows Server 2019 Standard
Description : (Recommended) This option omits most of the Windows graphical environment. Manage with a command prompt and PowerShell, or remotely with Windows Admin Center or other tools.
Size : 8,091,438,854 bytes
Index : 2
Name : Windows Server 2019 Standard (Desktop Experience)
Description : This option installs the full Windows graphical environment, consuming extra drive space. It can be useful if you want to use the Windows desktop or have an app that requires it.
Size : 14,313,685,692 bytes
Index : 3
Name : Windows Server 2019 Datacenter
Description : (Recommended) This option omits most of the Windows graphical environment. Manage with a command prompt and PowerShell, or remotely with Windows Admin Center or other tools.
Size : 8,090,160,854 bytes
Index : 4
Name : Windows Server 2019 Datacenter (Desktop Experience)
Description : This option installs the full Windows graphical environment, consuming extra drive space. It can be useful if you want to use the Windows desktop or have an app that requires it.
Size : 14,308,633,691 bytes
The operation completed successfully.
따라서 다음과 같이 명령을 수행했습니다.
C:\WINDOWS\system32> Dism /Online /Cleanup-Image /RestoreHealth /Source:WIM:d:\sources\install.wim:4 /LimitAccess
Deployment Image Servicing and Management tool
Version: 10.0.17763.1
Image Version: 10.0.17763.615
[==========================100.0%==========================] The restore operation completed successfully.
The operation completed successfully.
보는 바와 같이 정상적으로 완료가 되었고, 이후 sfc /scannow에서도 전에는 "was unable to fix"라면서 실패했던 반면 이제는 모두 복원했다고 나옵니다.
C:\WINDOWS\system32> sfc /scannow
Beginning system scan. This process will take some time.
Beginning verification phase of system scan.
Verification 100% complete.
Windows Resource Protection found corrupt files and successfully repaired them.
For online repairs, details are included in the CBS log file located at
windir\Logs\CBS\CBS.log. For example C:\Windows\Logs\CBS\CBS.log. For offline
repairs, details are included in the log file provided by the /OFFLOGFILE flag.
[이 글에 대해서 여러분들과 의견을 공유하고 싶습니다. 틀리거나 미흡한 부분 또는 의문 사항이 있으시면 언제든 댓글 남겨주십시오.]