Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile  


  1. Posts : 28,609
    Windows 10 (Pro and Insider Pro)
       #1130

    Kari said:
    Thanks Andre!

    OK, now I need to find out why it fails on all physical UEFI hardware I've tested. Might it be OEM / Retail related? All devices, mine and neighbour's I've tested have Retail licenses. Secure Boot is ruled out, that I know already.
    my test was on HP Elitedesk, so this makes it OEM

    Could fire up the old machine..
      My Computers


  2. Posts : 2,204
    WINDOWS 10 Pro x64 build 19042.685
       #1131

    After doing a system restore, for some reason, my mail app looks like this, without titlebars and with black background in the messages, I'm not sure if it's a bug or is that the application is preparing to receive elements of Fluent Design or something else, but I think I like it, of course, only on Skip Ahead!!
    Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile-10f.jpgAnnouncing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile-10f-2.jpgAnnouncing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile-10f3.jpg
      My Computer


  3. Posts : 1,524
    Windows 10 Pro (32-bit) 16299.15
       #1132

    Kari said:
    Geeks, anyone willing to test this?
    Hi Kari,
    It seems to work for me on a VM running 1703.
    It's in VirtualBox and in BIOS mode not UEFI.
    Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile-screenshot-9-.png
      My Computer


  4. Posts : 4,328
    Windows 10 preview 64-bit Home
       #1133

    Fabler2 said:
    Will have a go Kari but Bios and MBR only.
    This is the latest failure even though followed and entered your set commands again,


    Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile-trust-failure-2.png
      My Computers


  5. Posts : 56,489
    Multi-boot Windows 10/11 - RTM, RP, Beta, and Insider
       #1134

    Fabler2 said:
    This is the latest failure even though followed and entered your set commands again,


    Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile-trust-failure-2.png
    Unless I'm reading it wrong, it doesn't look like it failed. Did you get the .csv file on your desktop?
      My Computers


  6. Posts : 4,328
    Windows 10 preview 64-bit Home
       #1135

    Not on the desktop but found the log;

    Announcing Windows 10 Insider Fast Build 16257 PC + 15237 Mobile-csv..png
      My Computers


  7. Posts : 1,524
    Windows 10 Pro (32-bit) 16299.15
       #1136

    Kari said:
    Or did it fail?

    Attachment 149185

    I am mostly interested to hear if script fails on every UEFI based physical machine, and if it works on any VM or BIOS based physical machine?

    Thanks in advance!

    Kari
    Looks like the failing line is:
    Code:
    $devDetail = (Get-WMIObject -ComputerName $comp -Namespace root/cimv2/mdm/dmmap -class MDM_DevDetail_Ext01 -filter "InstanceID='Ext' AND ParentID='./DevDetail'")
    Where $comp is (if I understand correctly) defined by this ($comp is iterating through $Name, but presumably only one in this case).
    Code:
    $Name = @($env:ComputerName)
    I wonder if it's possible to run that command manually in isolation and learn something from that?
      My Computer


  8. Posts : 17,660
    Windows 10 Pro
       #1137

    DavidY said:
    Hi Kari,
    It seems to work for me on a VM running 1703.
    It's in VirtualBox and in BIOS mode not UEFI.
    Could you please check the .csv file and see if the device serial is in decimal or hexadecimal format?


    Fabler2 said:
    This is the latest failure even though followed and entered your set commands again,
    Screenshot shows no errors, which in case of PowerShell means it succeeded.


    f14tomcat said:
    Unless I'm reading it wrong, it doesn't look like it failed.
    Exactly.


    DavidY said:
    Looks like the failing line is:
    Yes, Get-WMIObject fails to collect data on some hardware. I've tested all possible alternatives I can think of, for instance replacing variables like $comp and $name with fixed strings. No difference; if it fails as a script on your device, that command also fails as standalone.
      My Computer


  9. Posts : 14,619
    Windows10
       #1138

    Kari said:
    Geeks, anyone willing to test this? Although a business / enterprise feature, this test can be done on every PC and VM, causing absolutely no harm. It only collects some data, saving it in a .csv (Comma Separated Values) on your desktop. You need to run W10 build 15063 or later.

    New Windows 10 deployment system for business and enterprise clients is called Windows AutoPilot. I have been testing it, when it works it's perfect, but I've met an interesting issue.

    How AutoPilot works is it registers devices to organisation using three values: device serial number, Windows product ID, and device hardware hash, same data which is base for so called hardware signature used to register W10 digital licenses. With new devices this is not an issue, organisations get this data from hardware manufacturers. When device is registered, Windows and all organisation's software can be deployed without IT department never seeing the device or even never being on same network.

    The problem is used devices. To get the data on a used device, user or admin needs to run a PowerShell script on each device which collects the data, saving it to a .csv file, which can then be uploaded to Microsoft Store for Business to register device. I have been trying and trying, having no issues in running the script and collecting required data on BIOS based physical hardware and both BIOS (Gen.1) and UEFI (Gen.2) Hyper-V virtual machines, but the script always fails on UEFI based physical hardware. I thought it to be Secure Boot related issue but have confirmed it's not.

    To test if the script works on your machine, if it manages to collect required data, simply run an elevated PowerShell and set script execution policy to Remote Signed:

    Set-ExecutionPolicy RemoteSigned -Scope Currentuser

    You will be asked to accept policy change. Press Y and Enter. Next, install the script:

    Install-Script -Name Get-WindowsAutoPilotInfo -Force

    If NuGet package provider for PowerShell is not installed, you will be asked if you want to install it. press Y and Enter.

    That's it. Now run the script:

    Get-WindowsAutoPilotInfo -OutputFile $env:userprofile\desktop\Test.csv

    Notice please: Script and required NuGet provider will together take less than 200 KB storage space on your hard disk.

    Was the Test.csv file created on desktop, does it contain device serial, product ID and hardware hash (.csv is normal text file, open with Notepad)?

    Attachment 149194

    Or did it fail?

    Attachment 149185

    I am mostly interested to hear if script fails on every UEFI based physical machine, and if it works on any VM or BIOS based physical machine?

    Thanks in advance!

    Kari
    lenovo laptop host pro 64bit 162571 - failed like yours

    uefi vm 64bit 162571 - failed in second line

    WARNING: Unable to download the list of available providers. Check your internet connection.
    PackageManagement\Install-PackageProvider : No match was found for the specified search
    criteria for the provider 'NuGet'. The package provider requires 'PackageManagement' and
    'Provider' tags. Please check if the specified package has the tags.
    At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:7468
    char:21
    + ... $null = PackageManagement\Install-PackageProvider -Name $script:N ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidArgument: (Microsoft.Power...PackageProvider:InstallP
    ackageProvider) [Install-PackageProvider], Exception
    + FullyQualifiedErrorId : NoMatchFoundForProvider,Microsoft.PowerShell.PackageManageme
    nt.Cmdlets.InstallPackageProvider

    PackageManagement\Import-PackageProvider : No match was found for the specified search
    criteria and provider name 'NuGet'. Try 'Get-PackageProvider -ListAvailable' to see if the
    provider exists on the system.
    At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\1.0.0.1\PSModule.psm1:7474
    char:21
    + ... $null = PackageManagement\Import-PackageProvider -Name $script:Nu ...
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidData: (NuGet:String) [Import-PackageProvider], Except
    ion
    + FullyQualifiedErrorId : NoMatchFoundForCriteria,Microsoft.PowerShell.PackageManageme
    nt.Cmdlets.ImportPackageProvider
      My Computer


  10. Posts : 4,328
    Windows 10 preview 64-bit Home
       #1139

    Screenshot shows no errors, which in case of PowerShell means it succeeded.

    Excellent Kari.
    ​Means I actually helped your highness? Thanks for the effort I went to... please don't mention it.
      My Computers


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 22:23.
Find Us




Windows 10 Forums