Get-Autopilotinfo.PS1 # Get the hash (if available) errors on Dynabook A40 Win10 pro 21H2

asked 2022-05-13T13:25:05.937+00:00
Adam Jacks 36 Reputation points

I have 20 Dynabook A40's, 18 of them have retrieved the hash file with no issues, 2 of them when running
$devDetail = (Get-CimInstance -CimSession $session -Namespace root/cimv2/mdm/dmmap -Class MDM_DevDetail_Ext01 -Filter "InstanceID='Ext' AND ParentID='./DevDetail'")

I get this error message on the devices ;

_Get-CimInstance : A general error occurred that is not covered by a more specific error code.
At D:\Autopilot\Get-WindowsAutoPilotInfo.ps1:209 char:23
... evDetail = (Get-CimInstance -CimSession $session -Namespace root/cimv ...
CategoryInfo : NotSpecified: (:) [Get-CimInstance], CimException
FullyQualifiedErrorId : MI RESULT 1,Microsoft.Management.Infrastructure.CimCmdlets.GetCimInstanceCommand_

The operating system is Windows 10 Pro 21H2, I only get the issue on these 2 devices, any Ideas/advice would be greatly appreciated.

Thank you.

Windows 10
Windows 10
A Microsoft operating system that runs on personal computers and tablets.
5,905 questions
Windows Autopilot
Windows Autopilot
A collection of Microsoft technologies used to set up and pre-configure new devices and to reset, repurpose, and recover devices.
232 questions
{count} votes

Accepted answer
  1. answered 2022-05-16T13:31:14.923+00:00
    Robert Florek 86 Reputation points

    It looks on global problem for Windows 10 registration via Autopilot, after install KB5013942 - 2022-05 Cumulative Update for Windows 10 Version 21H2.
    At this moment, only one solution is uninstall this KB via command wusa.exe /uninstall /KB:5013942.
    If device is enrolled (registered in Intune) then you can update device.

    For Windows 11 problem doesn't exist, even if KB 2022-05 is installed!

6 additional answers

Sort by: Most helpful
  1. answered 2022-05-16T01:37:33.8+00:00
    Crystal-MSFT 19,331 Reputation points Microsoft Employee

    @Adam Jacks , For the command in the Powershell script, it is used to collect hardware hash by querying the instance of the class "MDM_DevDetail_Ext01" under "root/cimv2/mdm/dmmap". Based on my checking on my machine, it exists on my win 10 machine.
    We can open Powershell and run as administrator, run the similar commands as below to see if the class is there or if the instance is there:
    Get-CimInstance -Namespace root/cimv2/mdm/dmmap -Class MDM_DevDetail_Ext01 -Filter "InstanceID='Ext' AND ParentID='./DevDetail'"

    If the instance is not there, I think there's maybe some issue on the OS. We suggest to do a clean install on the affected device to see if it can appear.

    Meanwhile, from the aspect view of Intune, maybe we can consider other enrollment methods on these affected device. Like Azure AD join +Auto enroll. Here is a link with more details for the reference:

    Hope it can help.

    If the answer is helpful, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    No comments

  2. answered 2022-05-25T05:35:38.123+00:00
    Joey Vldn 21 Reputation points

    Got this same issue. We're unable to remove KB5013942. Windows says this is a required security update and cannot be removed.

    Same issue while trying Get-WMIObject instead of Get-CimInstance

    (Get-WMIObject -Namespace root/cimv2/mdm/dmmap -Class MDM_DevDetail_Ext01 -Filter "InstanceID='Ext' AND ParentID='./DevDetail'").DeviceHardwareData

  3. answered 2022-05-25T17:36:54.26+00:00
    nick reid 1 Reputation point

    I'm also having this issue on Dell XPS laptops. The autopilot powershell script can't find the wmi entry for the hardware ID. Very frustrating as about to roll out a load of devices. Microsoft team please can you update us about this issue.

  4. answered 2022-06-02T06:59:07.48+00:00
    Joey Vldn 21 Reputation points

    FYI. The may updated 21H1 image does not have this issue. The 21H2 image still does.
    I could probably start with 21H1 as my base image and then update to the most recent feature update using update policies.

    Not the best but could work for some people..

    No comments