• ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
  • ×
    Information
    Need Windows 11 help?
    Check documents on compatibility, FAQs, upgrade information and available fixes.
    Windows 11 Support Center.
  • post a message
Guidelines
Are you having HotKey issues? Click here for tips and tricks.
Check out our WINDOWS 11 Support Center info about: OPTIMIZATION, KNOWN ISSUES, FAQs, VIDEOS AND MORE.
Locked

‎03-21-2025 04:13 AM

HP Recommended

HI.  

 

Thank you!!!   

 

OK found a file and downloaded the notepad but it makes no sense to me  so adding the code from the 19th March when the last time i tired the update manually.  Hopefully it makes some sense and maybe a clue to what is happening...

2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 DismApi.dll:                                            - DismInitializeInternal
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 DismApi.dll:                                            - DismInitializeInternal
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 DismApi.dll: Host machine information: OS Version=10.0.22631, Running architecture=amd64, Number of processors=4 - DismInitializeInternal
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 DismApi.dll: API Version 10.0.22621.4111 - DismInitializeInternal
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 DismApi.dll: Parent process command line: C:\WINDOWS\system32\svchost.exe -k netsvcs -p -s wuauserv - DismInitializeInternal
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 Input parameters: LogLevel: 2, LogFilePath: C:\Windows\Logs\WinREAgent\setupact.log, ScratchDirectory: (null) - DismInitializeInternal
2025-03-19 18:42:35, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\WinREAgent\setupact.log
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 Initialized GlobalConfig - DismInitializeInternal
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 Initialized SessionTable - DismInitializeInternal
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 Waiting for m_pInternalThread to start - CCommandThread::Start
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=16952 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=16952 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 m_pInternalThread started - CCommandThread::Start
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 Created g_internalDismSession - DismInitializeInternal
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 Input parameters: ImageFilePath: \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE\winre.wim - DismGetImageInfoInternal
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=16952 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=16952 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2025-03-19 18:42:35, Info                  DISM   PID=5092 TID=16952 Scratch directory set to 'C:\WINDOWS\TEMP\'. - CDISMManager::put_ScratchDir
2025-03-19 18:42:35, Info                  DISM   PID=5092 TID=16952 DismCore.dll version: 10.0.22621.1 - CDISMManager::FinalConstruct
2025-03-19 18:42:35, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\WinREAgent\setupact.log
2025-03-19 18:42:35, Info                  DISM   PID=5092 TID=16952 Successfully loaded the ImageSession at "C:\WINDOWS\SYSTEM32\Dism" - CDISMManager::LoadLocalImageSession
2025-03-19 18:42:35, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\WinREAgent\setupact.log
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=16952 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=16952 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=16952 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=16952 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=16952 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 Deleted g_internalDismSession - DismShutdownInternal
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 Shutdown SessionTable - DismShutdownInternal
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 DismApi.dll:                                          - DismShutdownInternal
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2025-03-19 18:42:35, Info                  DISM   API: PID=5092 TID=17096 DismApi.dll:                                          - DismShutdownInternal
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 DismApi.dll:                                            - DismInitializeInternal
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 DismApi.dll: <----- Starting DismApi.dll session -----> - DismInitializeInternal
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 DismApi.dll:                                            - DismInitializeInternal
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 DismApi.dll: Host machine information: OS Version=10.0.22631, Running architecture=amd64, Number of processors=4 - DismInitializeInternal
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 DismApi.dll: API Version 10.0.22621.4111 - DismInitializeInternal
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 DismApi.dll: Parent process command line: C:\WINDOWS\system32\svchost.exe -k netsvcs -p -s wuauserv - DismInitializeInternal
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 Input parameters: LogLevel: 2, LogFilePath: C:\Windows\Logs\WinREAgent\setupact.log, ScratchDirectory: (null) - DismInitializeInternal
2025-03-19 18:47:37, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\WinREAgent\setupact.log
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 Initialized GlobalConfig - DismInitializeInternal
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 Initialized SessionTable - DismInitializeInternal
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 Lookup in table by path failed for: DummyPath-2BA51B78-C7F7-4910-B99D-BB7345357CDC - CTransactionalImageTable::LookupImagePath
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 Waiting for m_pInternalThread to start - CCommandThread::Start
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=13032 Enter CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=13032 Enter CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 CommandThread StartupEvent signaled - CCommandThread::WaitForStartup
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 m_pInternalThread started - CCommandThread::Start
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 Created g_internalDismSession - DismInitializeInternal
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 Input parameters: ImageFilePath: \\?\GLOBALROOT\device\harddisk0\partition4\Recovery\WindowsRE\winre.wim - DismGetImageInfoInternal
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=13032 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=13032 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2025-03-19 18:47:37, Info                  DISM   PID=16436 TID=13032 Scratch directory set to 'C:\WINDOWS\TEMP\'. - CDISMManager::put_ScratchDir
2025-03-19 18:47:37, Info                  DISM   PID=16436 TID=13032 DismCore.dll version: 10.0.22621.1 - CDISMManager::FinalConstruct
2025-03-19 18:47:37, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\WinREAgent\setupact.log
2025-03-19 18:47:37, Info                  DISM   PID=16436 TID=13032 Successfully loaded the ImageSession at "C:\WINDOWS\SYSTEM32\Dism" - CDISMManager::LoadLocalImageSession
2025-03-19 18:47:37, Info                  DISM   Initialized Panther logging at C:\Windows\Logs\WinREAgent\setupact.log
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 GetReferenceCount hr: 0x0 - CSessionTable::RemoveSession
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 Refcount for DismSession= 1s 0 - CSessionTable::RemoveSession
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 Successfully enqueued command object - CCommandThread::EnqueueCommandObject
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=13032 ExecuteLoop: CommandQueue signaled - CCommandThread::ExecuteLoop
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=13032 Successfully dequeued command object - CCommandThread::DequeueCommandObject
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=13032 ExecuteLoop: Cancel signaled - CCommandThread::ExecuteLoop
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=13032 Leave CCommandThread::ExecuteLoop - CCommandThread::ExecuteLoop
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=13032 Leave CCommandThread::CommandThreadProcedureStub - CCommandThread::CommandThreadProcedureStub
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 Deleted g_internalDismSession - DismShutdownInternal
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 Shutdown SessionTable - DismShutdownInternal
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 DismApi.dll:                                          - DismShutdownInternal
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 DismApi.dll: <----- Ending DismApi.dll session -----> - DismShutdownInternal
2025-03-19 18:47:37, Info                  DISM   API: PID=16436 TID=9416 DismApi.dll:                                          - DismShutdownInternal

Also found these errors:

 

First one no surprise there as i knew this....

Installation Failure: Windows failed to install the following update with error 0x800F0801: Windows 11, version 24H2

 

Second one: Any idea what this all means please?

 

Unable to start a DCOM Server: {F3B5324B-98B2-4523-BBE5-1ABAB8B4D7D3} as Unavailable/Unavailable. The error:

"2147942403"

Happened while starting this command:

"C:\Program Files\WindowsApps\7EE7776C.LinkedInforWindows_3.0.42.0_x64__w1wdnht996qgy\LinkedIn\LinkedIn.exe" ----WindowsAppRuntimePushServer: -Embedding

 

This help to see why the file is erroring at 83%??

 

Thank you for the assistance..

Was this reply helpful? Yes No

‎03-23-2025 05:19 PM

HP Recommended

Hello 

has anyone got any help for me on these errors at all please??

thanks

Was this reply helpful? Yes No

‎03-23-2025 05:53 PM - edited ‎03-24-2025 07:46 AM

HP Recommended

@JRS1967,

 

Issue 1: Windows Update Failure (Error 0x800F0801):

 

The error 0x800F0801 means CBS_E_NOT_APPLICABLE, which indicates that the update either isn’t meant for the current system, has missing dependencies, or the system files required for installation are corrupted.

 

Steps to Fix:

 

  1. Run Windows Update Troubleshooter:

    • Go to Settings > System > Troubleshoot > Other troubleshooters.

    • Run Windows Update Troubleshooter.

  2. Enable .NET Framework (If Needed)

    • Open Command Prompt as Admin, then copy/paste and run: dism /online /enable-feature /featurename:NetFx3 /all /source:X:\sources\sxs /limitaccess

    • Replace X: with the Windows installation media drive letter.

  3. Check Windows Update Components

    • Open Command Prompt (Admin) and run one at a time:

      net stop wuauserv
       
      net stop cryptsvc
       
      net stop bits
       
      net stop msiserver
       
      ren C:\Windows\SoftwareDistribution SoftwareDistribution.old
       
      ren C:\Windows\System32\catroot2 catroot2.old
       
      net start wuauserv
       
      net start cryptsvc
       
      net start bits
       
      net start msiserver

    • Then restart the PC and try updating again.

  4. Use DISM and SFC to Repair System Files

    • Run in Command Prompt (Admin):

      dism /online /cleanup-image /restorehealth
      sfc /scannow

    • Restart and retry the update.

Issue 2: DCOM Error & WindowsApps LinkedIn.exe Failure:

 

The error 2147942403 corresponds to: ERROR_ACCESS_DENIED, meaning the DCOM component or app (LinkedIn.exe) lacks the necessary permissions.

 

Steps to Fix:

 

  1. Check DCOM Permissions

    • Press Win + R, type dcomcnfg and hit Enter.

    • Navigate to Component Services > Computers > My Computer > DCOM Config.

    • Locate the application {F3B5324B-98B2-4523-BBE5-1ABAB8B4D7D3} (or LinkedIn.exe).

    • Right-click > Properties > Security tab.

    • Under Launch and Activation Permissions, click Edit and ensure the correct permissions are set.

  2. Reinstall the LinkedIn Windows App

    • Open PowerShell (Admin) and run:

      Get-AppxPackage *LinkedInforWindows* | Remove-AppxPackage

    • Then reinstall from Microsoft Store.

  3. Check WindowsApps Permissions

    • Open C:\Program Files\WindowsApps and ensure SYSTEM and TrustedInstaller have full control.

  4. Run SFC and DISM (If Not Already Done)

    • sfc /scannow

    • dism /online /cleanup-image /restorehealth

 

Possible Cause for the 83% Error:


If the error occurs at 83%, it could be related to a permission issue during the update process or a failing Windows component. Running DISM and SFC should help resolve this. 🤞

 

Kind Regards,

 

NonSequitur777


1 person found this reply helpful
Was this reply helpful? Yes No

‎04-01-2025 09:44 AM

HP Recommended

Hi NonSequitur777

 

I have spent some time on this with Microsoft and they believe it is because my BIOS is locked and thus not updating...  I am going to search this on here, but have you any idea whi my BIOS is locked for updating?  I have tried to run but no luck.  i have F40 from 01.07.22 instead of F47 Rev a from 11.09.2024..

 

Any ideas?

 

Thanks

Was this reply helpful? Yes No

‎04-01-2025 10:11 AM

HP Recommended

@JRS1967,

 

Please understand that your issue(s) are at the fringe of what I am comfortable addressing, but as I understand the possible reasons for a locked BIOS, here are some possible fixes:

 

1. BIOS Administrator Password Blocking Update:

 

If a BIOS admin password is set, the update may be restricted.

 

✅ Check & Remove BIOS Password:

  1. Restart the laptop and press F10 to enter BIOS.

  2. Go to Security > Setup Password.

  3. If a password is set, try removing it or resetting it (if possible).

  4. Save changes and restart.

 

If you don’t know the password, the only way to reset it is through HP support (proof of ownership required).

2. Secure Boot or BitLocker Blocking BIOS Update:

 

BIOS updates sometimes fail if Secure Boot is enabled or BitLocker interferes.

 

✅ Disable Secure Boot:

  1. Enter BIOS (F10 at boot).

  2. Go to Advanced > Secure Boot Configuration.

  3. Disable Secure Boot, then Save & Exit.

  4. Try the BIOS update again.

✅ Suspend BitLocker (If Enabled):

  1. Open Command Prompt (Admin) and run:

    manage-bde -protectors -disable C:

  2. Restart your laptop and attempt the BIOS update.

3. HP Sure Start / BIOS Rollback Protection Preventing Update:

 

HP Sure Start or rollback protection can block BIOS updates.

 

✅ If Applicable, Disable HP Sure Start & BIOS Rollback Protection:

 

  1. Enter BIOS (F10 at boot).

  2. Navigate to Advanced > Secure Boot Configuration.

  3. Locate BIOS Rollback Protection and disable it.

  4. Also check HP Sure Start settings under Security and disable protection temporarily.

  5. Save and exit.

4. Using the Wrong BIOS Update Method:

 

If trying to update through Windows and failing, use the USB method instead.

 

✅ BIOS Update via USB (Recommended for Locked BIOS):

  1. Download the BIOS Update (F47 Rev A) from HP’s Support Page.

  2. Create a Bootable USB:

  3. Boot from the USB:

    • Restart and press F9 at startup.

    • Select USB Drive and follow on-screen instructions.

5. BIOS or Firmware Corruption:

 

If previous BIOS updates failed, the system might be stuck in a locked state.

 

✅ Perform BIOS Recovery:

  1. Turn off the laptop.

  2. Hold Win + B, then press and hold the power button.

  3. Continue holding Win + B for about 10-15 seconds, then release.

  4. The BIOS recovery screen should appear. Follow the instructions to recover the BIOS.

Next Steps To Take:

 

  1. Check BIOS password & Secure Boot settings

  2. Try updating via USB if Windows installer fails

  3. Use BIOS Recovery if all else fails

 

If you need help finding the correct BIOS update file, you should verify your exact product name and current BIOS version by running in CMD as Administrator: wmic bios get smbiosbiosversion

 
Let me know if this helped you.
 
Kind Regards,
 
NonSequitur777

1 person found this reply helpful
Was this reply helpful? Yes No
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.
Didn't find what you were looking for? Ask the community
† The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the <a href="https://www8.hp.com/us/en/terms-of-use.html" class="udrlinesmall">Terms of Use</a> and <a href="/t5/custom/page/page-id/hp.rulespage" class="udrlinesmall"> Rules of Participation</a>.