cancel
Showing results for 
Search instead for 
Did you mean: 
MaDDeRHaTTeR
New member
2 1 0 0
Message 1 of 2
685
Flag Post

The Straw that broke the camel's laptop was called: MoAppHang: That is when things got Confusing!

HP Recommended
HP NOTEBOOK
Microsoft Windows 10 (64-bit)

i saw someone fix (I think he fixed it) by doing this:

 

"Upgrading to the latest fails because "a deprecated version of this product is installed" and "uninstall the current version first". I have to manually uninstall. Then reinstalling the latest Write Filter from Update Center works."

 

My issues really all started with the HP CENTERS BIOS Update. Somehow, things were FINE before that. Things have slowly been falling apart since. Do I need a patch? How can I uninstall it?? I am not "fluent" in code by any means... I connect dots that seem logical plus a bit of research... MOST of this stuff is way over my head. Please be patient and honest with me. I would appreciate any help. Here are some bits of code that got me this far:

 

Info CSI 0000000c Warning: Unable to repair payload file ([l:26]'MSFT_MpThreatCatalog.cdxml') for component ([l:96 ml:140]'amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.1_none_b620cb061e8a941c') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2019-08-14 00:48:54, Info CSI 0000000d Hashes for file member [l:28]'MSFT_MpThreatDetection.cdxml' do not match.
Expected: {l:32 ml:33 b:a19bf000eb950ddd8438c30562c0fa6f3c0848432f55a219ef3d79b302aa6cf1}.
Actual: {l:32 b:3c082a55cd0e2d835764bb55c35292277b3c3a7a909543123a9b75bddf7ef20f}.
2019-08-14 00:48:54, Info CSI 0000000e Warning: Unable to repair payload file ([l:28]'MSFT_MpThreatDetection.cdxml') for component ([l:96 ml:140]'amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.1_none_b620cb061e8a941c') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
2019-08-14 00:48:54, Info CSI 0000000f Hashes for file member [l:23]'MSFT_MpPreference.cdxml' do not match.
Expected: {l:32 ml:33 b:8861d55dd84b45902d2fbd8f73fd663be669f589105ce656000b77496ece0de6}.
Actual: {l:32 b:dd557986b51074f3e4b7d5c0923903bf10ba919a1235605f5cba8a49b05ef07d}.
2019-08-14 00:48:54, Info CSI 00000010 Warning: Unable to repair payload file ([l:23]'MSFT_MpPreference.cdxml') for component ([l:96 ml:140]'amd64_windows-defender-management-powershell_31bf3856ad364e35_10.0.18362.1_none_b620cb061e8a941c') from backups directory with disposition (2). A backup file may not exist or may be corrupt. Falling back to WU.
CBS Not all CSI corruption was fixed, create CorruptionDetectedDuringAcr flag for slow mode reset
2019-08-14 00:49:07, Info CBS CheckSur: hrStatus: 0x0 [S_OK], download Result: 0x0 [S_OK]
2019-08-14 00:49:07, Info CBS Count of times corruption detected: 1
2019-08-14 00:49:07, Info CBS Failed to delete current corruption first found value. [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2019-08-14 00:49:07, Info CBS Failed getting last corruption first found time [HRESULT = 0x80070490 - ERROR_NOT_FOUND]
2019-08-14 00:49:07, Info CBS Seconds between initial corruption detections: -1
2019-08-14 00:49:07, Info CBS Seconds between corruption and repair: -1
2019-08-14 00:49:08, Info CBS Reboot mark cleared
2019-08-14 00:49:08, Info CBS Winlogon: Simplifying Winlogon CreateSession notifications
2019-08-14 00:49:08, Info CBS Winlogon: Deregistering for CreateSession notifications
2019-08-14 00:49:08, Info CBS Exec: Processing complete, session(Corruption Detecting): 30757487_1247916451 [HRESULT = 0x00000000 - S_OK]
2019-08-14 00:49:08, Info CBS Engine: Try to wake up thread for execution: 15620
2019-08-14 00:49:08, Info CBS Session: 30757487_1247916451 finalized. Reboot required: no [HRESULT = 0x00000000 - S_OK]
2019-08-14 00:49:08, Info CBS Engine: Thread ready for execution: 15620
2019-08-14 00:49:08, Info CBS Exec: Session processing started. Client: Manual, Session(DISM Package Manager Provider Store Corruption Detect/Repair): 30757487_2127541166
2019-08-14 00:49:08, Info CBS Reboot mark set
2019-08-14 00:49:08, Info CBS Winlogon: Registering for CreateSession notifications
2019-08-14 00:49:08, Info CBS FLOW: Entering stage: CheckCbs
2019-08-14 00:49:08, Info CSI 0000127b Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 0000127c Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 0000127d Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 0000127e Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 0000127f Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 00001280 Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 00001281 Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 00001282 Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 00001283 Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 00001284 Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 00001285 Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 00001286 Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 00001287 Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 00001288 Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 00001289 Direct SIL provider: Number of files opened: 1.
2019-08-14 00:49:08, Info CSI 0000128a Direct SIL provider: Number of files opened: 2.
2019-08-14 00:49:08, Info CSI 0000128b

CBS Appl: detect Parent, Package: Microsoft-Windows-FailoverCluster-Management-Tools-FOD-Package~31bf3856ad364e35~amd64~~10.0.18362.1, Parent: Microsoft-Windows-EditionPack-Professional-Package~31bf3856ad364e35~amd64~~10.0.18362.1, Disposition = Detect, VersionComp: EQ, BuildComp: GE, RevisionComp: GE, Exist: present
2019-08-13 18:37:02, Info CBS Appl: detectParent: parent found: Microsoft-Windows-EditionPack-Professional-Package~31bf3856ad364e35~amd64~~10.0.18362.1, state: Staged
2019-08-13 18:37:02, Info CBS Appl: detectParent: parent found: Microsoft-Windows-EditionPack-Professional-Package~31bf3856ad364e35~amd64~~10.0.18362.239, state: Staged
2019-08-13 18:37:02, Info CBS Appl: detectParent: parent found: Microsoft-Windows-EditionPack-Professional-Package~31bf3856ad364e35~amd64~~10.0.18362.267, state: Staged
2019-08-13 18:37:02, Info CBS Appl: Evaluating package applicability for package Microsoft-Windows-FailoverCluster-Management-Tools-FOD-Package~31bf3856ad364e35~amd64~~10.0.18362.1, applicable state: Staged
2019-08-13 18:37:02, Info CBS FOD: Package found on the server, but not applicable to the system: \\?\C:\WINDOWS\Servicing\InboxFodMetadataCache\metadata\Rsat.FailoverCluster.Management.Tools~~1.0.mum
2019-08-13 18:37:02,

Method 1:
Run sfc scan: System File Checker is a utility in Microsoft Windows that allows users to scan for and restore corruptions in Windows system files.
1. Press Windows + X from desktop.
2. Then click on Command Prompt (Admin)
3. Then type in
sfc/scannow
and press Enter

RESULT:

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

 

... help? ...  😮

1 REPLY 1
Riddle_Decipher
HP Support Agent
HP Support Agent
31,166 31,117 2,618 3,994
Message 2 of 2
Flag Post
HP Recommended

@MaDDeRHaTTeR Since the issue began after the recent BIOS update, I recommend we start with reverting to the last known good/working bios configuration using the steps in this link: Click here for details, once done, you should be able to use the computer without any of these issues.

 

If the issue continues to occur, make use the USB drive suggested in the link to recover the old BIOS.

 

P.S: Welcome to HP Community 😉

 

Let me know how that pans out,

If you feel I was helpful, simply click on Accept as Solution to help the community grow,

That said, I will have someone follow-up on this to ensure you've been helped,

Just in case you don't get back to us within 24 - 48hrs, and have a good day, ahead.

Riddle_Decipher
I am an HP Employee

0 Kudos
Warning Be alert for scammers posting fake support phone numbers and/or email addresses on the community. If you think you have received a fake HP Support message, please report it to us by clicking on "Flag Post".
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation