Forum Widgets
Latest Discussions
ADK 18362.1 DISM Fails Offline Install for kb4497936+kb4505057 for WinRE.wim
DISM fails to install 14/May/2019 LCU on Winre.wim KB4497936 (Released 11/5/2019 with KB4500109) KB4505057 (Released 20/5/2019) The image is unmounted, however DISM continues to install package, using host system registry, not mounted image registry. 2019-05-15 22:26:30, Info DISM DISM.EXE: <----- Starting Dism.exe session -----> 2019-05-15 22:26:30, Info DISM DISM.EXE: 2019-05-15 22:26:30, Info DISM DISM.EXE: Host machine information: OS Version=10.0.18362, Running architecture=amd64, Number of processors=8 2019-05-15 22:26:30, Info DISM DISM.EXE: Dism.exe version: 10.0.18362.1 2019-05-15 22:26:30, Info DISM DISM.EXE: Executing command line: "D:\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\dism.exe" /Unmount-Image /MountDir:E:\WinROG\mount\RE /DISCARD 2019-05-15 22:26:30, Info DISM DISM Provider Store: PID=2660 TID=3056 Getting the collection of providers from a local provider store type. - CDISMProviderStore::GetProviderCollection 2019-05-15 22:26:30, Info DISM DISM Provider Store: PID=2660 TID=3056 Connecting to the provider located at D:\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\FolderProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2019-05-15 22:26:30, Info DISM DISM Provider Store: PID=2660 TID=3056 Connecting to the provider located at D:\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\SiloedPackageProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2019-05-15 22:26:30, Info DISM DISM Provider Store: PID=2660 TID=3056 Connecting to the provider located at D:\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\FfuProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2019-05-15 22:26:30, Info DISM DISM Provider Store: PID=2660 TID=3056 Connecting to the provider located at D:\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\WimProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2019-05-15 22:26:30, Info DISM DISM Provider Store: PID=2660 TID=3056 Connecting to the provider located at D:\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\VHDProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2019-05-15 22:26:30, Info DISM DISM Provider Store: PID=2660 TID=3056 Connecting to the provider located at D:\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\ImagingProvider.dll. - CDISMProviderStore::Internal_LoadProvider 2019-05-15 22:26:30, Warning DISM DISM Provider Store: PID=2660 TID=3056 Failed to load the provider: D:\Windows Kits\10\Assessment and Deployment Kit\Deployment Tools\AMD64\DISM\MetaDeployProvider.dll. - CDISMProviderStore::Internal_GetProvider(hr:0x8007007e) 2019-05-15 22:26:30, Info DISM DISM.EXE: Got the collection of providers. Now enumerating them to build the command table. 2019-05-15 22:26:30, Info DISM DISM.EXE: Attempting to add the commands from provider: DISM Log Provider 2019-05-15 22:26:30, Info DISM DISM.EXE: Attempting to add the commands from provider: FolderManager 2019-05-15 22:26:30, Info DISM DISM.EXE: Attempting to add the commands from provider: SiloedPackageManager 2019-05-15 22:26:30, Info DISM DISM.EXE: Succesfully registered commands for the provider: SiloedPackageManager. 2019-05-15 22:26:30, Info DISM DISM.EXE: Attempting to add the commands from provider: FfuManager 2019-05-15 22:26:30, Info DISM DISM.EXE: Succesfully registered commands for the provider: FfuManager. 2019-05-15 22:26:30, Info DISM DISM.EXE: Attempting to add the commands from provider: WimManager 2019-05-15 22:26:30, Info DISM DISM.EXE: Succesfully registered commands for the provider: WimManager. 2019-05-15 22:26:30, Info DISM DISM.EXE: Attempting to add the commands from provider: VHDManager 2019-05-15 22:26:30, Info DISM DISM.EXE: Attempting to add the commands from provider: GenericImagingManager 2019-05-15 22:26:30, Info DISM DISM.EXE: Succesfully registered commands for the provider: GenericImagingManager. 2019-05-15 22:26:30, Info DISM DISM FFU Provider: PID=2660 TID=3056 [E:\WinROG\mount\RE] is not recognized by the DISM FFU provider. - CFfuImage::Initialize 2019-05-15 22:26:30, Info DISM DISM Imaging Provider: PID=2660 TID=3056 The provider FfuManager does not support CreateDismImage on E:\WinROG\mount\RE - CGenericImagingManager::CreateDismImage 2019-05-15 22:26:30, Info DISM DISM VHD Provider: PID=2660 TID=3056 [E:\WinROG\mount\RE] is not recognized by the DISM VHD provider. - CVhdImage::Initialize 2019-05-15 22:26:30, Info DISM DISM Imaging Provider: PID=2660 TID=3056 The provider VHDManager does not support CreateDismImage on E:\WinROG\mount\RE - CGenericImagingManager::CreateDismImage [2660] ImageUnmarshallHandle: Reconstituting wim at E:\WinROG\CustOEM-DaRT-RE-G751.wim. [2660] ImageUnmarshallHandle: Reconstituting wim at E:\WinROG\CustOEM-DaRT-RE-G751.wim. [2660] ImageUnmarshallHandle: Reconstituting wim at E:\WinROG\CustOEM-DaRT-RE-G751.wim. [11720] Received unmount request for image with guid e5043866-3c22-45c8-be93-1f56cf9ce0b4. [11720] Unmount for image at E:\WinROG\mount\RE complete. [2660] [0x8007000e] StateStoreGetMountedImageWimbootEntries:(1285): Not enough memory resources are available to complete this operation. [2660] Encountered file with excess reparse data. Id 0x00050000000236ad [2660] Encountered file with excess reparse data. Id 0x0005000000023712 [2660] Encountered file with excess reparse data. Id 0x00050000000237b1 [2660] Encountered file with excess reparse data. Id 0x00050000000237b2Windows AI Platform: Windows ML APIs, DirectML APIs, Microsoft Compute Driver Model (MCDM)
As the industry continues to focus on Artificial Intelligence, the Windows 10 platform (starting with Windows 10 1803 and continuing through Windows 10 1903) is bringing the best tools for performing local, high-performance machine learning inferencing with the Windows AI Platform: Windows ML APIs - enabling machine learning inferencing DirectML APIs - providing operator-level access to ONNX 1.3 standard resources Microsoft Compute Driver Model (MCDM) - a driver model for compute and AI specific silicon for Windows This video from Build 2019 gives a great overview of the Windows AI platform.
Signing kernel driver fails with Cab Signature validation failed with error: 0x80090008
As of 14.09.2021 I am getting error when submitting drivers for signing. When I submit the CAB file, I get Cab Signature validation failed with error: 0x80090008. What causes the issue is a simple parameter of signtool.exe when I sign the CAB file. Obviously, Microsoft have changed the requirements for what type of CAB signing they accept. Till yesterday, my signtool.exe options were "/a /tr http://timestapprovider/ /td sha256 .. etc" After I got the error I started reading I found out I'm missing one more parameter : "/fd sha256" So, it should be like : "/a /fd sha256 /tr http://timestampprovider/ /td sha256 ... etc" To be honest I don't know how I have missed the change, but now it works. Hope this helps. Cheers, Daniel
UEFI GOP mode
Hello: About UEFI GOP mode test Topology Selection: • UEFI must reliably detect all the displays that are connected to the POST adapter. The Pre-OS screen can only be displayed on a display connected to the POST adapter. •In case multiple displays are detected, UEFI must display the Pre-OS screen based on the following logic: System with an Integrated display(Laptop, All In One, Tablet): UEFI must display the Pre-OS screen only on the integrated display If the laptop system Pre-OS screen is also displayed on the external monitor simultaneously, will this violate the regulations?SysVAD Virtual Audio Driver Sample updated
The Microsoft SysVAD Virtual audio Device Deriver (SYSVAD) sample code, used to demonstrate how to develop a WDM audio driver which exposes support for multiple devices, was updated on 4 December 2019. Changes include: Removal of the Phone Audio sample Addition of a WaveTest public sample Modification of the componentized audio samples to include the addComponent directive For more details and to download the sample code, please visit the SysVAD Virtual Audio Device Driver Sample page on docs.microsoft.com.Welcome to WinHEC Online!
Welcome to the new home of WinHEC Online, home to the Windows Hardware Certification and Hardware Dev Center blogs, and the Microsoft Tech Community for builders and partners creating hardware for the Intelligent Edge with Microsoft technologies, from Server to Sensor. Discussions, announcements and blog posts will be found covering topics important to hardware development, including: Azure IoT Edge, Azure Sphere, Windows Server, Windows IoT, Windows 10 desktops and more! Continue discussions started during WinHEC events, ask new questions, get insights from Microsoft, and learn about the latest manufacturing guidance for released Microsoft software. If you are new to Microsoft Tech Communities, these introductory links will get you started: Microsoft Tech Community Code of Conduct Microsoft Tech Community - Getting Started Join in!HLK-Testing: How to set "QueryValidationDriverFolder" parameter for HLK Test named "ApiValidator"
When starting the HLK-Test named "ApiValidator" test parameter settings are not offered to me. The test therefore fails because QueryValidationDriverFolder parameter string is empty. When I export the Test-Run and modify the parameter in the exported file run.cmd to indicate the correct folder, the test is successful in the exported TestRun, but when I trigger the test via the HLK-Studio it again fails. WHERE am I supposed to set this parameter so it is used when running via HLK-Studio? Thanks in advance, Erich Smutny
Driver Signing for pre-Windows 2016 questions
I have some questions about what the recommendations are for generating a signed driver for Windows 2016 and earlier. I set up the HCK test server (2008 R2) and test system(2012 R2), installed my driver, ran the appropriate tests, and generated an HCKX. I do NOT have access to my EV Certificate on the HCK test server. I generated an unsigned .hckx file, and am trying to use the HLK Studio (which DOES have access to our EV Certificate) to sign it. Ideally, I'd like to end up with a driver that runs on Windows 2008 R2 (x64) through Windows 2022. We've run the HLK tests against Windows 2019 successfully, and I am able to submit that to the Hardware Dev Center and get a signed driver that works on 2016, 2019, and 2022. I was attempting to use the "merge" capabilities in the HLK Studio to bring in the .hckx file that we created on the HCK controller system. To do this, I created a new project and chose "Connect", and loaded the previous .hlkx file. Then I chose "merge" and added the .hckx file. I cleared the Drivers Folder that was pointing to my user TEMP directory, and added a single Drivers folder that contains the driver that we tested on both systems (2012 R2 and 2019). The Driver Properties lists both "Windows Server v10.0 17763" and "Windows Server v6.3" - I highlighted both of those, and added the English locale. Then I added a Symbols folder. I signed the resulting .hlkx file with our EV Certificate and uploaded it for signing at the HW Dev Center. The resulting download contains a signed copy of the driver, but the Microsoft signature is SHA256 (which I don't believe will work on 2012 R2). I tried installing it on a 2012 R2 system - won't boot. Any idea what I need to do differently to get this to work? Thanks! Ernie CoskreyThe same version, different driver date driver update problem
Hi、technical advisor I would like to confirm whether the driver date has a higher priority than the driver version when updating the driver through windows update. For example: I have a driver, the version is 2.0.0.354, the driver date is 2021/10/22, because the test found that there is a problem with this driver, the manufacturer changed the inf file and re-passed WHQL, and the driver version is still 2.0.0.354, It's just that the driver date has changed to 2021/10/25, I released a new driver through WU, it was a critical release, and I checked "Automatically delivered during Windows Upgrades" and "Automatically delivered to all applicable systems", this new driver Will it be downloaded and installed automatically? Will the new driver be automatically downloaded and installed for devices that have activated the Windows operating system, while the new drivers will only be downloaded and not automatically installed for devices that have not been activated for OEM testing?thank you very much!
