F FenixSoars New member Joined Sep 20, 2022 Posts 1 Sep 20, 2022 #1 Hi all, I'm about ready to pull my hair out with this one. I have a 2016 Datacenter Server running that refuses to install the 2022-09 CU. I've run DISM and SFC. DISM found corruption and I have repaired that with providing a WIM source. sfc /scannow fails at 39% showing Code: 2022-09-20 10:35:27, Error CSI 00002a24@2022/9/20:16:35:27.190 (F) onecore\base\wcp\componentstore\deltastore.cpp(2483): Error STATUS_INVALID_PARAMETER originated in function ComponentStore::CRawStoreLayout::DecompressFile expression: Parameter check failed [gle=0x80004005] I'm pulling the update from a WSUS server and have also tried the direct installation package from the Microsoft Update Catalog. Any ideas on this parameter that seems to be invalid that DISM can't fix? As an aside, when trying to install the update, I receive an error of poqexec not being able to update an unfound update file.. I think the HRESULT code is 0x80070005 File_Not_Found
Hi all, I'm about ready to pull my hair out with this one. I have a 2016 Datacenter Server running that refuses to install the 2022-09 CU. I've run DISM and SFC. DISM found corruption and I have repaired that with providing a WIM source. sfc /scannow fails at 39% showing Code: 2022-09-20 10:35:27, Error CSI 00002a24@2022/9/20:16:35:27.190 (F) onecore\base\wcp\componentstore\deltastore.cpp(2483): Error STATUS_INVALID_PARAMETER originated in function ComponentStore::CRawStoreLayout::DecompressFile expression: Parameter check failed [gle=0x80004005] I'm pulling the update from a WSUS server and have also tried the direct installation package from the Microsoft Update Catalog. Any ideas on this parameter that seems to be invalid that DISM can't fix? As an aside, when trying to install the update, I receive an error of poqexec not being able to update an unfound update file.. I think the HRESULT code is 0x80070005 File_Not_Found
x BlueRobot Administrator Staff member Joined May 7, 2013 Posts 10,222 Location %systemroot% Sep 30, 2022 #2 Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps. 2. Try running sfc /scannow just like you have in the past. 3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square icon on the toolbar as shown below. 4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine. 5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or WeTransfer.
Capture Process Monitor Trace 1. Download and run Process Monitor. Leave this running while you perform the next steps. 2. Try running sfc /scannow just like you have in the past. 3. Stop Process Monitor as soon as it fails. You can simply do this by clicking the square icon on the toolbar as shown below. 4. Select the File menu...Save... and save the file to your desktop. This is likely the default location. The name (unless changed) will be LogFile.PML. This is fine. 5. Zip up and provide the link to the LogFile.PML file as well as your CBS.log Examples of services to upload to are Dropbox or OneDrive or WeTransfer.