BSOD crash with CRITICAL_PROCESS_DIED cant boot sr run sfc /scannow

Page 3 of 6 FirstFirst 12345 ... LastLast
  1.    30 May 2018 #21

    ok so I downloaded the files from here:
    UUP dump
    This is the version 1709 (16299.371)x86 and created an install.wim image from these files.

    I then copied the install.wim to D:\sources2\install.wim and tried the following in offline mode from a bootable USB. THe bootable USB has a newer Win 10 Pro version than the files we're trying to fix.
    I made sure to use the correct install.wim 16299.371

    X:\Sources>DISM /Image:C:\ /Cleanup-Image /RestoreHealth /Source:d:\sources2\install.wim:1 /ScratchDir:C:\Scratch

    After reaching approximately 9%, there was an error 87 with the DISM.log
    "An error occurred while processing the command.
    Ensure that the command line arguments are valid. For more information, review the log file"
    Log file is attached as dism3.txt

    There are lots of CBS_E_XML_PARSER_FAILURE errors and a few other errors.
    Not sure where to go from here.

    I've also verified that the mounted c:\windows image is the same version:
    Note I copied the config software file from the affected machine, copied it to USB and loaded / unloaded the registry hive under a key named PKTEST which was then unloaded.

    [HKEY_LOCAL_MACHINE\PKTEST\Microsoft\Windows NT\CurrentVersion]
    "CurrentType"="Multiprocessor Free"
    "ProductName"="Windows 10 Pro"

    (173)hex = (371)decimal
    BSOD crash with CRITICAL_PROCESS_DIED cant boot sr run sfc /scannow Attached Files
      My ComputerSystem Spec

  2. philc43's Avatar
    Posts : 3,824
    64bit Win 10 Pro ver 1809 Build 17763.253 and W10 Insider Build 18312
       30 May 2018 #22

    The key info from the log file appears to be towards the end:

    Checking System Update Readiness.
    (p)	CBS MUM Corrupt			HyperV-Guest-IcSvcExt-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			HyperV-Guest-Shutdown-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			HyperV-UX-UI-62-vm-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			HyperV-UX-UI-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			LanguageFeatures-WordBreaking-en-legacy-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-BusinessScanning-Feature-Package-admin~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-Client-Drivers-drivers-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-Client-Drivers-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-Client-Features-Package00116~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-Client-Features-Package0017~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-Dedup-ChunkLibrary-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-Desktop-Shared-Drivers-onecoreuap-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-Desktop-Shared-Drivers-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-Embedded-EmbeddedLogon-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-Embedded-UnifiedWriteFilter-base-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-IIS-WebServer-AddOn-2-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-IIS-WebServer-AddOn-2-ServerCommon-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-IIS-WebServer-AddOn-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-IIS-WebServer-AddOn-ServerCommon-Package~31bf3856ad364e35~x86~en-US~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-IIS-WebServer-Package~31bf3856ad364e35~x86~en-US~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-IIS-WebServer-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-IIS-WebServer-ServerCommon-Package~31bf3856ad364e35~x86~en-US~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-IIS-WebServer-ServerCommon-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-LanguageFeatures-TextToSpeech-en-us-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-MSMQ-Client-Package~31bf3856ad364e35~x86~en-US~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-MultiPoint-Connector-Package~31bf3856ad364e35~x86~en-US~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-NetFx-Shared-WCF-HttpActivation~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-NetFx-Shared-WCF-PipeActivation~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-NetFx-VCRedist-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-NetFx3-WCF-OC-Package~31bf3856ad364e35~x86~en-US~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-NetFx4-US-OC-Package~31bf3856ad364e35~x86~en-US~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-OfflineFiles-base-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-PhotoBasic-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-PortableWorkspaces-Creator-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-Printing-LocalPrinting-Home-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-Spelling-Dictionaries-en-us-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-TabletPC-IHM-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-TerminalServices-UsbRedirector-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Microsoft-Windows-TextPrediction-Package~31bf3856ad364e35~x86~~10.0.16299.15
    (p)	CBS MUM Corrupt			Package_309_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_310_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_311_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_313_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_314_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_317_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_318_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_319_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_320_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_321_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_322_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_323_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_324_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_325_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_326_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_327_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_328_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_328_for_KB4058258~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_329_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_330_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_331_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_382_for_KB4093112~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_404_for_KB4093112~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_405_for_KB4093112~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_408_for_KB4093112~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_410_for_KB4074588~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_411_for_KB4074588~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_412_for_KB4093112~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_413_for_KB4074588~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_414_for_KB4074588~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_415_for_KB4074588~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_416_for_KB4074588~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_417_for_KB4074588~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_418_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_419_for_KB4074588~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_419_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_420_for_KB4074588~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_421_for_KB4090913~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_422_for_KB4090913~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_423_for_KB4074588~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_425_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_438_for_KB4074588~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_477_for_KB4074588~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_48_for_KB4074608~31bf3856ad364e35~x86~~16299.212.1.0
    (p)	CBS MUM Corrupt			Package_540_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_541_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_543_for_KB4058258~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_545_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_546_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_547_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_548_for_KB4093112~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_551_for_KB4093112~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_553_for_KB4093112~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_556_for_KB4058258~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_557_for_KB4058258~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_557_for_KB4093112~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_558_for_KB4058258~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_558_for_KB4093112~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_559_for_KB4093112~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_561_for_KB4058258~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_561_for_KB4093112~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_562_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_562_for_KB4058258~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_566_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_567_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_567_for_KB4090913~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_569_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_570_for_KB4056892~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_58_for_KB4074608~31bf3856ad364e35~x86~~16299.212.1.0
    (p)	CBS MUM Corrupt			Package_58_for_KB4099989~31bf3856ad364e35~x86~~16299.367.1.0
    (p)	CBS MUM Corrupt			Package_59_for_KB4074608~31bf3856ad364e35~x86~~16299.212.1.0
    (p)	CBS MUM Corrupt			Package_59_for_KB4099989~31bf3856ad364e35~x86~~16299.367.1.0
    (p)	CBS MUM Corrupt			Package_608_for_KB4074588~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_60_for_KB4074608~31bf3856ad364e35~x86~~16299.212.1.0
    (p)	CBS MUM Corrupt			Package_60_for_KB4099989~31bf3856ad364e35~x86~~16299.367.1.0
    (p)	CBS MUM Corrupt			Package_618_for_KB4074588~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_61_for_KB4074608~31bf3856ad364e35~x86~~16299.212.1.0
    (p)	CBS MUM Corrupt			Package_621_for_KB4090913~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_62_for_KB4074608~31bf3856ad364e35~x86~~16299.212.1.0
    (p)	CBS MUM Corrupt			Package_63_for_KB4074608~31bf3856ad364e35~x86~~16299.212.1.0
    (p)	CBS MUM Corrupt			Package_63_for_KB4090914~31bf3856ad364e35~x86~~16299.251.1.0
    (p)	CBS MUM Corrupt			Package_64_for_KB4074608~31bf3856ad364e35~x86~~16299.212.1.0
    (p)	CBS MUM Corrupt			Package_65_for_KB4074608~31bf3856ad364e35~x86~~16299.212.1.0
    (p)	CBS MUM Corrupt			Package_692_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_710_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_711_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_712_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_714_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_716_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_717_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_718_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_719_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_720_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_721_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_722_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_723_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_724_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_730_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_743_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_744_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_745_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_746_for_KB4088776~31bf3856ad364e35~x86~~
    (p)	CBS MUM Corrupt			Package_for_KB4074608~31bf3856ad364e35~x86~~16299.212.1.0
    (p)	CBS MUM Corrupt			Package_for_RollupFix~31bf3856ad364e35~x86~~16299.192.1.9
    (p)	CBS MUM Corrupt			Windows-Defender-Core-Group-Package~31bf3856ad364e35~x86~~10.0.16299.15
    Operation: Detect and Repair 
    Operation result: 0x80070057
    Last Successful Step: CBS store detection completes.
    Total Detected Corruption:	144
    	CBS Manifest Corruption:	144
    	CBS Metadata Corruption:	0
    	CSI Manifest Corruption:	0
    	CSI Metadata Corruption:	0
    	CSI Payload Corruption:	0
    Total Repaired Corruption:	0
    	CBS Manifest Repaired:	0
    	CSI Manifest Repaired:	0
    	CSI Payload Repaired:	0
    	CSI Store Metadata refreshed:	False
    Total Operation Time: 14 seconds.
    2018-05-29 22:07:51, Info                  CBS    CheckSur: hrStatus: 0x80070057 [E_INVALIDARG], download Result: 0x800f081f [CBS_E_SOURCE_MISSING]
    I suspect you need a cumulative update to add the missing packages which are presumably not in the install.wim

    See the following for a similar problem:
      My ComputersSystem Spec

  3.    30 May 2018 #23

    Ok - I looked through the 144 errors reported in the previous DISM, and not knowing where to start, I decided to pick a random corrupt package to install that appeared in a lot of entries, in this case KB4088776. Of course maybe I should have picked the earliest package, or maybe a cumulative image - please let me know, definitely need some advice here.

    I downloaded the x86 version of KB4088776, and extracted the .cab file from here.
    Microsoft Update Catalog

    I then used the DISM command to try and fix items related to KB4088776

    DISM /image:c:\ /Add-Package /PackagePath:e:\packages\KB4088776\ /ScratchDir:C:\Scratch

    I got error 0x800f0900, and the attached DISM4.txt

    Assuming that I'm willing to go package by package to try and fix all 144 errors, please let me know what you would suggest next. I realize that trying a random KB4088776 package was by no means the best idea at this point, but I thought I'd try it to see what would happen.

    Assuming that there is some kind of laborious, but straightforward procedure that would have a high probability of success - I think it's worth trying. At some point when enough stuff is fixed - some of may literally start fixing itself.

    Any guidance would be very much appreciated.
    BSOD crash with CRITICAL_PROCESS_DIED cant boot sr run sfc /scannow Attached Files
      My ComputerSystem Spec

  4.    31 May 2018 #24

    here is an Excel file that sorts 144 errors by package and date released

    I've tried installing KB4056892 package which was the earliest date package listed in the corrupt list.
    DISM /image:c:\ /Add-Package /PackagePath:e:\packages\KB4056892\ /ScratchDir:C:\Scratch

    It failed as well, attached is dism5.txt
    BSOD crash with CRITICAL_PROCESS_DIED cant boot sr run sfc /scannow Attached Files
      My ComputerSystem Spec

  5. philc43's Avatar
    Posts : 3,824
    64bit Win 10 Pro ver 1809 Build 17763.253 and W10 Insider Build 18312
       31 May 2018 #25

    I will have to look into this a little later but for now all I can suggest is that I was not thinking that you would need to go through all the packages but simply install one cumulative update that is dated later than all the packages listed in the 144 errors. In this way it should update everything and maybe some extra ones too.

    Perhaps @Bree can take a look at this as he is an expert at understanding the DISM failures which have happened in the past.
      My ComputersSystem Spec

  6. Bree's Avatar
    Posts : 9,954
    10 Home x64 (1809) (10 Pro on 2nd pc)
       31 May 2018 #26

    This seems to be the key error....
    2018-05-30 23:38:02, Info                  CBS    Manifest parsing error at line: 1, context: 
    �����SVW�D$3�Pjj���d��\$�\$ ��<b��\$��b�� [HRESULT = 0x800f0900 - CBS_E_XML_PARSER_FAILURE]
    2018-05-30 23:38:02, Info                  CBS    Failed to parse the manifest from the buffer. [HRESULT = 0x800f0900 - CBS_E_XML_PARSER_FAILURE]
    2018-05-30 23:38:02, Error                 CBS    Failed to parse package manifest: \c:\Windows\Servicing\Packages\Package_309_for_KB4056892~31bf3856ad364e35~x86~~ [HRESULT = 0x800f0900 - CBS_E_XML_PARSER_FAILURE]
    These package manifest .mum files are supposed to be readable text files, not a string of ����� as line 1 appears to be. Your manifest for KB4056892 appears to be corrupt, not sure where to go next. You could try downloading it again from the catalog.
      My ComputersSystem Spec

  7. philc43's Avatar
    Posts : 3,824
    64bit Win 10 Pro ver 1809 Build 17763.253 and W10 Insider Build 18312
       31 May 2018 #27

    Good spot @Bree but I did not see the corrupt text in the earlier dism.txt files that the OP had provided. The parsing errors were there though.
      My ComputersSystem Spec

  8.    31 May 2018 #28

    Just so we're on the same page - this is an offline DISM package install on the C: drive from a bootable 1803 Win 10 USB.

    Just so I understand correctly, when I download the .msu from the catalog and extract it, there are 4 files

    So far I've been running DISM /add-package and only copied 2 files to USB:

    Is copying the .cab sufficient?

    Also I discovered that KB4056892 has been eventually superseded by KB4103714, and KB4103714 does not have any later updates - should I try running that instead?
      My ComputerSystem Spec

  9.    31 May 2018 #29

    I tried DISM /add-package with the latest 1709 KB4103714 update.
    I think it's the latest 1709 since it's 5/21/2018 and not not superseded by any other packages.

    Attached is the DISM6.txt log for this run.
    The funny characters are not in the DISM log, but according to the log it appears it still has trouble reading the package manifest.
    BSOD crash with CRITICAL_PROCESS_DIED cant boot sr run sfc /scannow Attached Files
      My ComputerSystem Spec

  10.    31 May 2018 #30

    I've looked through the 144 errors and the windows update catalog, and looks like cumulative packages KB4132650 and KB4103714 superseed all the other ones.

    I've already tried KB4103714, will try KB4132650 in the evening Pacific Time.

    Would be interested in any ideas on KB4103714 failures from previous post.
    Attached is the update revision of excel file which shows which package superseed the corrupted packages.
    BSOD crash with CRITICAL_PROCESS_DIED cant boot sr run sfc /scannow Attached Files
      My ComputerSystem Spec

Page 3 of 6 FirstFirst 12345 ... LastLast

Related Threads
Hey there, computer overlords, Thanks for checking this out. TL;DRóBSOD, "INACCESSIBLE_BOOT_DEVICE" when updating to 1607. Restored from backup and tried again. Ran chkdsk. sfc /scannow fails (see log link). Drivers updated. I let Windows...
CRITICAL_PROCESS_DIED on boot in General Support
Hi. My mom's laptop is crashing on boot with a CRITICAL_PROCESS_DIED error. It boots in Safe Mode but most things are unresponsive: no windows menu, command prompt opens right away but admin prompt takes 10-20 minutes to open, so do task manager...
Hello! I've been having issues with a Critical_Process_Died BSOD for several weeks now and have already spent quite a bit of time troubleshooting it, to no avail. The start of my problems did not coincide with any major hardware or software changes....
Hello, I am having BSOD's again. I am getting the above error on the blue screen. It's worse now though because it never makes it past the "collecting data" it just freezes at 0%. After I shut it down and restart it manually, it gives me a...
Solved BSOD Critical_Process_Died in BSOD Crashes and Debugging
The OS (win10Pro) is an upgrade from Win7Ultimate and this BSOD issue only started happening this morning. Unfortunately, my last image is from Friday so I'm not sure that will be of any help either. The diagnostic file is attached. One thing that...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 10:36.
Find Us