In windows 11 enterprise edition, I have events 103 AESMService: Platform Services initialization failed due to DAL error. How to stop these messages?

Anonymous
2024-03-15T14:26:35+00:00

I'm running an hp all-in-one and am getting event id 103, AESMService: Platform Services initialization failed due to DAL error. I believe I have followed all the usual steps to resolve to no avail., including:

sfc /scannow

DISM /Online /Cleanup-Image /RestoreHealth

chkdsk

I still have the same error this morning,

<Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**">

  • <System> <Provider Name="AESMService" Guid="{ce6e83d3-a7d9-4a91-96e0-e018ad574610}" /><EventID>103</EventID><Version>0</Version><Level>3</Level><Task>0</Task><Opcode>0</Opcode><Keywords>0x8000000000000000</Keywords><TimeCreated SystemTime="2024-03-15T14:09:00.0176140Z" /><EventRecordID>190</EventRecordID><Correlation /><Execution ProcessID="1864" ThreadID="7900" /><Channel>SGX/Admin</Channel><Computer>DESKTOP-ENSLEYS</Computer><Security UserID="S-1-5-18" /></System>
  • <EventData> <Data Name="attrUnicodeString">Platform Services initialization failed due to DAL error</Data></EventData> </Event>

I also have an error 28,

<Event xmlns="**http://schemas.microsoft.com/win/2004/08/events/event**">

  • <System> <Provider Name="Microsoft-Windows-Kernel-EventTracing" Guid="{b675ec37-bdb6-4648-bc92-f3fdc74d3ca2}" /><EventID>28</EventID><Version>0</Version><Level>2</Level><Task>3</Task><Opcode>25</Opcode><Keywords>0x8000000000000a20</Keywords><TimeCreated SystemTime="2024-03-15T14:06:50.4097255Z" /><EventRecordID>30</EventRecordID><Correlation /><Execution ProcessID="968" ThreadID="972" /><Channel>Microsoft-Windows-Kernel-EventTracing/Admin</Channel><Computer>DESKTOP-ENSLEYS</Computer><Security UserID="S-1-5-18" /></System>
  • <EventData> <Data Name="ProviderGuid">{77811378-e885-4ac2-a580-bc86e4f1bc93}</Data><Data Name="ErrorCode">3221225477</Data></EventData> </Event>

This has been persistent and I have tried everything to fix it.

Any help on steps to solve these issues would be greatly appreciated.

Thank you!

***moved from Windows / Windows 11 / Performance and system failures***

Windows for business | Windows Client for IT Pros | User experience | Remote desktop services and terminal services

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question. To protect privacy, user profiles for migrated questions are anonymized.

0 comments No comments
{count} votes

16 answers

Sort by: Most helpful
  1. Anonymous
    2024-03-22T19:04:56+00:00

    I have decided to buy a new computer, as this one has the wrong BIOS and cannot be upgraded (the BIOS installer at HP will not down grade the BIOS). It has the incorrect BIOS and that must be why these errors are continuing.

    It is not only frustrating, but unnecessary. But now I am forced to s[pend $ to get a new computer.

    Adios,

    D, L. Ensley II,

    windows 11

    HP All-in-One 22-c0083w

    TO WRAP UP:

    Reported problems on the AESMservice on my HP All-in-One 20"

    Warning in SGX/Admin log: AESMService: Platform Services initialization failed due to DAL error

    http://schemas.microsoft.com/win/2004/08/events/event"> - 205 0 2 0 0 0x4000000000000000 88 SGX/Diagnostic DESKTOP-HOMEPC - Failed to load QE3: 0x4004 Error ID 205: AESMService: [load_qe X:\windows-trunk\dcap-trunk\dcap_source\QuoteGeneration\quote_wrapper\quote\qe_logic.cpp:721] Error, call sgx_create_enclave QE fail [load_qe], SGXError:4004.

    http://schemas.microsoft.com/win/2004/08/events/event"> - 205 0 2 0 0 0x4000000000000000 87 SGX/Diagnostic DESKTOP-HOMEPC - [load_qe X:\windows-trunk\dcap-trunk\dcap_source\QuoteGeneration\quote_wrapper\quote\qe_logic.cpp:721] Error, call sgx_create_enclave QE fail [load_qe], SGXError:4004.

    My bandaid fix is to stop logging the AESMService error 103, on the 20" HP: Modify registry key to set Enabled to 0:

    Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-Application{ce6e83d3-a7d9-4a91-96e0-e018ad574610}

    After this fix, I find no errors and no warnings.(!)

    Other applied fixes included:

    1. At first opportunity, run sfc /scannow and DISM. Reboot. sfc /scannow DISM /Online /Cleanup-Image /RestoreHealth
    2. Disable the DeviceSetupManager service. This eliminates a slew of errors from the logs that are sourced from DeviceSetupManager.
    3. Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\wscsvc Set delayedautostart to 0. This eliminates the windows.security.center warnings events 10010.

    In the WMI autologger section, the following event ID's were disabled from being logged:

    1. Event 6155 which are 10 different LSA warning messages that I could not get to stop. Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System{199fe037-2b82-40a9-82ac-e1d46c792b99}
    2. Event 360 Windows Hello, which is not physically supported by my PC so to suppress the Windows Hello log file warnings that will continually fire otherwise, since neither of the PC's has full Windows Hello capability. Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-Application{23b8d46b-67dd-40a3-b636-d43e50552c6d}
    3. Event WMI 63 disabled WMI logging.

    Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-Application{1edeee53-0afe-4609-b846-d8c0b2075b1f}

    1. Event ID 219 plug and play for missing devices. These warnings fire twice per reboot for the two expected plug and play slots which are normally filled but not in my pc. So prevent logging the (this is only occurring on the 24" HP PC).

    Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System{9c205a39-1250-487d-abd7-e831c6290539}

    1. Error Event 28 (this one happens on every PC):
      Computer\HKEY\_LOCAL\_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-System\{b675ec37-bdb6-4648-bc92-f3fdc74d3ca2}
      
    2. To stop logging the AESMService error 103, on the 20" HP: Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WMI\Autologger\EventLog-Application{ce6e83d3-a7d9-4a91-96e0-e018ad574610}
    3. The WLAN error 10002 regarding Rtlihvs.dll by removing the IHVExtensions key that is in the non-depository area of the registry under the currentcontrol section Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class{4d36e972-e325-11ce-bfc1-08002be10318}\0002\Ndi\IHVExtensions
    4. Removed the Windows.Client.WebExperience package via PowerShell (admin) winget\ uninstall “windows web experience pack” This was causing a certain DCOM 10016 error about it.
    5. Errors 5858 in the WMI Activity log folder (not verified yet). From admin cmd run net stop winmgmt winmgmt /verifyrepository if repository is inconsistent, run
       winmgmt /salvagerepository        
      
       winmgmt /resetrepository             
      
      net start winmgmt

    Following these suggestions has led me to a 0 errors, 0 warnings condition on both HP All-in-Ones in my posession. The 24" one did not generate any ASEM errors, and had all the components of the Intel MD Components installer alread installed. Also, it is an SSD drive which is a lot faster. There are some deep down Event 5858 errors when things start up on my 20". I do not know if they are just benign, they do not appear on the Administrative Events log, nor do they appear to bog down the PC. I consider the issue solved, as the specific 205 errors appear to be related to a BIOS that needs fixing from HP. They will need to address this specific issue with a special BIOS patch or release. I believe it to be the case because I did verify with an HP tech that my computer has the correct BIOS for it. It is not the PC's fault, but HP's that this error persists because the BIOS is not supporting the AESMservice correctly. Maybe if they address the problem, get the fix, then release the fixed BIOS this problem will disappear. Right now, I am keeping the mask on until HP fixes the BIOS. Thanks again for your effort and continued support.

    Best regards,

    Donald L. Ensley II

    Computer Science Engineer

    0 comments No comments