Problem Using WOR-Flasher

[SeaDog58]

Setup:

• Which version of Windows you chose: Windows Pro 11
• Raspberry Pi model: 5
• Name of SD card you tried to flash (some are too slow or too small): Using 500gb SSD connected to USB
• What day you first downloaded wor-flasher: Updated 22 May 2024
• What linux operating system you are using to run wor-flasher on. (Raspberry Pi OS, Twister OS, Debian, etc): Raspberry PI OS

Procedure:

Latest attempt to Flash Windows Pro 11 to a Raspberry Pi 5 using WoR-Flasher • Steps completed without error until “Downloading Windows ESD Image”. • Then errors in downloading numerous CUIDs. Error code 8. • Continued to download 4.8gb of data. • Download verified. • Extracted image.esd to /home/John/wor-flasher-files/winfiles_22631.2861_en_us • Preparations completed with GDK error which I understand is not critical. • I re-booted Raspbian OS after changing the boot order to start with NVMe. • In “Windows on Raspberry Pre-installation Environment”. • Displayed “Preparing Disk”. o Western Digital 1TB SN750 NVMe Internal Gaming SSD Solid State Drive - Gen3 PCIe, M.2 2280, 3D NAND, Up to 3,470 MB/s - WDS100T3X0C o It is in an external enclosure with a USB 3 cable. o The drive in this enclosure worked fine on a PC running Windows Pro 11. o After about 12 hours, there was no additional activity. • I moved the NVMe drive to a PC running Windows Pro 11 and used Disk Management to explore the drive. o There were 3 partitions – 953mb FAT32, 16.76gb exFAT, 913.38gb not formatted. o In the exFAT partition there is an install.wim file (5.1 gb) which apparently was never executed. • I have attached the Log file from the Pre-installation Environment. • Is there any way to use install.wim while drive is connected to PC? Any help would be appreciated. WoR-PE.log

[schau80269]

This is not an issue with WoR-Flasher, but rather a strange HW/SW compatibility issue. I've had massive trouble installing Win11 Pro ARM64 24H2 into NVMe SSDs mounted into USB enclosures that feature the Realtek RTL9210B chip inside (e.g. Sabrent EC-SNVE) for my Raspberry Pi 5 (and Orange Pi 5 Plus). Problem symptoms were similar to yours. I then changed to a different USB enclosure with Jmicron JMS583 chip inside (e.g. 1st gen Plugable USBC-NVME) and OS installation proceeded normally to completion. For some unknown reason, Win11 ARM64 OS installation bits just do not play nice with RTL9210B-based NVMe USB enclosures, but Win11 x86-64 OS (for Intel & AMD) does not have this issue. Even updating the firmware of the Realtek USB enclosure did not help. Switching to Jmicron-based USB enclosure is the only realistic workaround I've found. Tricky part is how to identify whether a USB enclosure uses Realtek or Jmicron chip as the manufacturers never volunteer this info.

[SeaDog58]

Thanks. This is very helpful. I have found that Plugable uses both JMicron and RealTek chipsets in various versions. I have asked Plugable Support how to identify the correct version. I’ll see what they have to say.

From: schau80269 @.> Sent: Monday, June 24, 2024 10:07 PM To: Botspot/wor-flasher @.> Cc: SeaDog58 @.>; Author @.> Subject: Re: [Botspot/wor-flasher] Problem Using WOR-Flasher (Issue #158)

This is not an issue with WoR-Flasher, but rather a strange HW/SW compatibility issue. I've had massive trouble installing Win11 Pro ARM64 24H2 into NVMe SSDs mounted into USB enclosures that feature the Realtek RTL9210B chip inside (e.g. Sabrent EC-SNVE) for my Raspberry Pi 5 (and Orange Pi 5 Plus). Problem symptoms were similar to yours. I then changed to a different USB enclosure with Jmicron JMS583 chip inside (e.g. 1st gen Plugable USBC-NVME) and OS installation proceeded normally to completion. For some unknown reason, Win11 ARM64 OS installation bits just do not play nice with RTL9210B-based NVMe USB enclosures, but Win11 x86-64 OS (for Intel & AMD) does not have this issue. Even updating the firmware of the Realtek USB enclosure did not help. Switching to Jmicron-based USB enclosure is the only realistic workaround I've found. Tricky part is how to identify whether a USB enclosure uses Realtek or Jmicron chip as the manufacturers never volunteer this info.

— Reply to this email directly, view it on GitHubhttps://github.com/Botspot/wor-flasher/issues/158#issuecomment-2187801541, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGHY4P3L5UHMH42JFQLSU73ZJDGDLAVCNFSM6AAAAABIPQGL5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBXHAYDCNJUGE. You are receiving this because you authored the thread.Message ID: @.**@.>>

[schau80269]

Another option is to connect an NVMe SSD directly to the Raspberry Pi 5 with a m.2 PCIe hat. With latest bootloader installed into the Pi 5, WoR-Flasher works great installing Win11 ARM64 24H2 OS directly into NVMe SSDs. The performance is good too, especially with the PCIe configured to gen 3 speed.

[SeaDog58]

I just spoke to Plugable this morning. With their enclosure they now use a RealTek chipset. They used the JMicron chipset in an early version which is not out of stock and not available. They did have a good idea.

“I have not tested with Windows on Raspberry Pi (ARM) however I do not normally recommend this enclosure for direct connection to the Raspberry Pi. NVMe SSDs require a great deal of power and often switch on/off quite quickly, I have found in testing with the Pi 3 and Pi 4 that this causes the USB host controller to go offline and disconnects the drive during some read and most write operations. Using an independently powered USB 3.0 hub between the enclosure and the Raspberry Pi should resolve this disconnection issue.” From Plugable Support.

I have ordered a powered USB 3.0 hub and will try it with the enclosure I have already. I did try the NVMe SSD in a Hat for the Pi, but had the same problem with trying to install Windows 11 ARM. I will let you know the results of my testing. It may be a power problem.

John

From: schau80269 @.> Sent: Tuesday, June 25, 2024 12:55 PM To: Botspot/wor-flasher @.> Cc: SeaDog58 @.>; Author @.> Subject: Re: [Botspot/wor-flasher] Problem Using WOR-Flasher (Issue #158)

Another option is to connect an NVMe SSD directly to the Raspberry Pi 5 with a m.2 PCIe hat. With latest bootloader installed into the Pi 5, WoR-Flasher works great installing Win11 ARM64 24H2 OS directly into NVMe SSDs. The performance is good too, especially with the PCIe configured to gen 3 speed.

— Reply to this email directly, view it on GitHubhttps://github.com/Botspot/wor-flasher/issues/158#issuecomment-2189461550, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGHY4PY3LTUS5MRWXY5HKDLZJGOE7AVCNFSM6AAAAABIPQGL5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBZGQ3DCNJVGA. You are receiving this because you authored the thread.Message ID: @.**@.>>

[SeaDog58]

I have given up trying to get WOR-Flasher to work with an NVME drive. I tried a powered USB hub twice with a 500gb NVMe card and a 256gb NVMe card and the Windows installation failed in both cases. I then installed the official Raspberry M2 hat (I had another M2 hat but decided to try the official one) using the 256gb NVMe card and that failed.

WOR-Flasher sets up the boot partition and a partition with the install.wim file on the NVMe card. As near as I can tell the problem arises when it is formatting and trying to install the wim file on a third partition. I have tried formatting the whole NVMe cards as ExFat on a PC before trying WOR-Flasher. That didn’t help.

I do have Windows 11 installed on a USB SSD using WOR-Flasher and that works. I think there is a definite problem with Flasher when using NVMe. It looks to me like Flasher was developed primarily for SD cards. I suspect a problem with the script for DiskPart in the final stages.

John

From: John Poindexter Sent: Tuesday, June 25, 2024 1:54 PM To: Botspot/wor-flasher @.>; Botspot/wor-flasher @.> Subject: RE: [Botspot/wor-flasher] Problem Using WOR-Flasher (Issue #158)

I just spoke to Plugable this morning. With their enclosure they now use a RealTek chipset. They used the JMicron chipset in an early version which is not out of stock and not available. They did have a good idea.

“I have not tested with Windows on Raspberry Pi (ARM) however I do not normally recommend this enclosure for direct connection to the Raspberry Pi. NVMe SSDs require a great deal of power and often switch on/off quite quickly, I have found in testing with the Pi 3 and Pi 4 that this causes the USB host controller to go offline and disconnects the drive during some read and most write operations. Using an independently powered USB 3.0 hub between the enclosure and the Raspberry Pi should resolve this disconnection issue.” From Plugable Support.

I have ordered a powered USB 3.0 hub and will try it with the enclosure I have already. I did try the NVMe SSD in a Hat for the Pi, but had the same problem with trying to install Windows 11 ARM. I will let you know the results of my testing. It may be a power problem.

John

From: schau80269 @.**@.>> Sent: Tuesday, June 25, 2024 12:55 PM To: Botspot/wor-flasher @.**@.>> Cc: SeaDog58 @.**@.>>; Author @.**@.>> Subject: Re: [Botspot/wor-flasher] Problem Using WOR-Flasher (Issue #158)

Another option is to connect an NVMe SSD directly to the Raspberry Pi 5 with a m.2 PCIe hat. With latest bootloader installed into the Pi 5, WoR-Flasher works great installing Win11 ARM64 24H2 OS directly into NVMe SSDs. The performance is good too, especially with the PCIe configured to gen 3 speed.

— Reply to this email directly, view it on GitHubhttps://github.com/Botspot/wor-flasher/issues/158#issuecomment-2189461550, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGHY4PY3LTUS5MRWXY5HKDLZJGOE7AVCNFSM6AAAAABIPQGL5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBZGQ3DCNJVGA. You are receiving this because you authored the thread.Message ID: @.**@.>>

[schau80269]

WoR-Flasher is NOT at fault for your Win11 OS installation failures with Raspberry Pi 5 and NVMe SSD. There is a known issue with the Win11 inbox NVMe storage driver (stornvme.sys) not working with RPi5, so installations using stock (unmodified) OS installation bits will fail, and even if you somehow make it through the installation, the OS will likely fail during OOBE and never reach the desktop properly. WoR-Flasher simply gets badly tripped up by this issue.

To use WoR-Flasher to directly install Win11 into NVMe SSD, it is necessary to replace the stornvme driver residing in the OS installation files (boot.wim & install.wim) on the USB installation media. A version of stornvme driver v6 "50%" provided recently by developer digdoug2 on Discord works well with RPi5 and I've had multiple successful installations and stable OS operation with several different NVMe SSD brands and models attached via m.2 Hat.

Attached is a script I wrote that uses DISM to automate the replacement of stornvme.sys for boot.wim & install.wim, and optionally inject 3rd-party ARM64 device drivers (there are none currently for RPi5). Once the boot.wim & install.wim files are processed by this script, Win11 installation into NVMe SSD connected to RPi5 should work.

Inject_ARM64_Drivers_Replace_stornvme_Win11ARM64.zip

[Botspot]

This looks promising. @schau80269 If you are interested in getting this added to the wor-flasher for everyone, let me know!

[schau80269]

@Botspot Feel free to add stornvme driver replacement functionality to WoR-Flasher! Replacing the inbox stornvme driver is critical in getting Win11 ARM64 OS to install successfully for ARM SBCs such as Raspberry Pi 5 and Rockchip RK3588-based boards such as the Orange Pi 5 series. With the replacement stornvme driver in place, WoR-Flasher typically completes OS installation into NVMe SSD on RPi5 in less than 6 minutes, and subsequent OS bootups are trouble free. The ARM64 driver injections in my script are mostly for my Orange Pi 5 Plus. Pre-injected RK3588 ARM64 drivers don't seem to affect Raspberry Pi 5 installations. I also inject a ARM64 driver for Realtek USB-to-Ethernet adapters (1GbE & 2.5GbE) so RPi5 can have internet connectivity during the OOBE setup. The v6 "50%" stornvme driver provided by digdoug2 serves the RPi5 extremely well. I've had zero crashes. Unfortunately, it's different for my Orange Pi 5 Plus where there are still random DPC_Watchdog_Violation BSOD crashes with NVMe SSD, so Win11 ARM64 24H2 currently runs with NVMe SSDs on Raspberry Pi 5 better than with RK3588 SBCs.

[SeaDog58]

I’m not familiar with the download sources for the stornvme driver v6. I have searched but can’t find. Where can I find it? John

From: schau80269 @.> Sent: Thursday, July 4, 2024 12:15 AM To: Botspot/wor-flasher @.> Cc: SeaDog58 @.>; Author @.> Subject: Re: [Botspot/wor-flasher] Problem Using WOR-Flasher (Issue #158)

WoR-Flasher is NOT at fault for your Win11 OS installation failures with Raspberry Pi 5 and NVMe SSD. There is a known issue with the Win11 inbox NVMe storage driver (stornvme.sys) not working with RPi5, so installations using stock (unmodified) OS installation bits will fail, and even if you somehow make it through the installation, the OS will likely fail during OOBE and never reach the desktop properly. WoR-Flasher simply gets badly tripped up by this issue. To use WoR-Flasher to directly install Win11 into NVM SSD, it is necessary to replace the stornvme driver residing in the OS installation files (boot.wim & install.wim) on the USB installation media. A recent version of stornvme driver v6 "50%" provided recently by developer digdoug2 on Discord works well with RPi5 and I've had multiple successful installations and stable OS operation with several different NVMe SSD brands and models attached via m.2 Hat. Attached is a script I wrote that uses DISM to automate the replacement of stornvme.sys for boot.wim & install.wim, and optionally inject 3rd-party ARM64 device drivers (there are none currently for RPi5). Once the boot.wim & install.wim files are processed by this script, Win11 installation into NVMe SSD connected to RPi5 should work. Inject_ARM64_Drivers_Replace_stornvme_Win11ARM64.ziphttps://github.com/user-attachments/files/16093267/Inject_ARM64_Drivers_Replace_stornvme_Win11ARM64.zip

— Reply to this email directly, view it on GitHubhttps://github.com/Botspot/wor-flasher/issues/158#issuecomment-2208087939, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGHY4P2HROSGFDEBNINZE4LZKTD37AVCNFSM6AAAAABIPQGL5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBYGA4DOOJTHE. You are receiving this because you authored the thread.Message ID: @.**@.>>

[schau80269]

stornvme v6 driver was posted to the "Windows on R" Discord server by digdoug2. Attached is a copy.

stornvme_v6.zip

[SeaDog58]

Thanks. I’m working a bit over my head…smile. Where is storahci driver? John

From: schau80269 @.> Sent: Thursday, July 4, 2024 11:15 AM To: Botspot/wor-flasher @.> Cc: SeaDog58 @.>; Author @.> Subject: Re: [Botspot/wor-flasher] Problem Using WOR-Flasher (Issue #158)

stornvme v6 driver was posted to the "Windows on R" Discord server by digdoug2. Attached is a copy.

stornvme_v6.ziphttps://github.com/user-attachments/files/16100646/stornvme_v6.zip

— Reply to this email directly, view it on GitHubhttps://github.com/Botspot/wor-flasher/issues/158#issuecomment-2209211527, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGHY4PZHWOKZANLWHQ3A6ETZKVRGTAVCNFSM6AAAAABIPQGL5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGIYTCNJSG4. You are receiving this because you authored the thread.Message ID: @.**@.>>

[schau80269]

storahci driver is not used for Raspberry Pi 5 with NVMe SSD, so no driver replacement is needed.

[SeaDog58]

Thank you. I was confused by your CMD file. I will try it out tomorrow.

From: schau80269 @.> Sent: Thursday, July 4, 2024 4:03 PM To: Botspot/wor-flasher @.> Cc: SeaDog58 @.>; Author @.> Subject: Re: [Botspot/wor-flasher] Problem Using WOR-Flasher (Issue #158)

storahci driver is not used for Raspberry Pi 5 with NVMe SSD, so no driver replacement is needed.

— Reply to this email directly, view it on GitHubhttps://github.com/Botspot/wor-flasher/issues/158#issuecomment-2209514217, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGHY4P7IYFV4VQ3WXAMSPODZKWS6LAVCNFSM6AAAAABIPQGL5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGUYTIMRRG4. You are receiving this because you authored the thread.Message ID: @.**@.>>

[schau80269]

Here's a replacement storahci driver to keep the CMD script happy.

storahci.zip

[SeaDog58]

Thanks. I ran the CMD file without it and it complained a bit, but it did produce the modified intall.wim and boot.wim. Tomorrow I will try Flasher again. John

From: schau80269 @.> Sent: Thursday, July 4, 2024 4:26 PM To: Botspot/wor-flasher @.> Cc: SeaDog58 @.>; Author @.> Subject: Re: [Botspot/wor-flasher] Problem Using WOR-Flasher (Issue #158)

Here's a replacement storahci driver to keep the CMD script happy.

storahci.ziphttps://github.com/user-attachments/files/16102680/storahci.zip

— Reply to this email directly, view it on GitHubhttps://github.com/Botspot/wor-flasher/issues/158#issuecomment-2209532689, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGHY4PZXERHTACEIQIDOZELZKWVVZAVCNFSM6AAAAABIPQGL5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGUZTENRYHE. You are receiving this because you authored the thread.Message ID: @.**@.>>

[SeaDog58]

I have tried running Flasher again several times with and without the storahci driver. This morning I tried the new install.wim and boot.wim files produced by your CMD script including the storachi driver. The first test was to a 500gb NVME SSD connected via a USB port. The process got to the Windows Preinstallation and hung up. The log file showed it got to the point: “Launch Diskpart.exe with /s “X:\diskpart.script”. Then I tried to flash to a 256gb NVME SSD inserted in a Raspberry official M2 Hat. It did not get to the Windows Preinstallation. In both cases the NVME SSDs were partitioned with a BOOT partition and one other which included install.wim, but Windows 11 Pro was not installed.

I ran your CMD script again and saved the results in the attached logs – one is a capture of the CMD screen and the other is the DISM log. Note there are several errors. The resulting install.wim and boot.wim files may not be complete. One set of errors reference the ARM64 drivers. It appears it is looking in Windows\system32\drivers.

John

From: John Poindexter Sent: Thursday, July 4, 2024 7:23 PM To: Botspot/wor-flasher @.***> Subject: RE: [Botspot/wor-flasher] Problem Using WOR-Flasher (Issue #158)

Thanks. I ran the CMD file without it and it complained a bit, but it did produce the modified intall.wim and boot.wim. Tomorrow I will try Flasher again. John

From: schau80269 @.**@.>> Sent: Thursday, July 4, 2024 4:26 PM To: Botspot/wor-flasher @.**@.>> Cc: SeaDog58 @.**@.>>; Author @.**@.>> Subject: Re: [Botspot/wor-flasher] Problem Using WOR-Flasher (Issue #158)

Here's a replacement storahci driver to keep the CMD script happy.

storahci.ziphttps://github.com/user-attachments/files/16102680/storahci.zip

— Reply to this email directly, view it on GitHubhttps://github.com/Botspot/wor-flasher/issues/158#issuecomment-2209532689, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGHY4PZXERHTACEIQIDOZELZKWVVZAVCNFSM6AAAAABIPQGL5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMBZGUZTENRYHE. You are receiving this because you authored the thread.Message ID: @.**@.>>

 C:\Windows\System32>"C:\WOR\Win11_ARM64_WIM\Inject_ARM64_Drivers_Replace_stornvme_Win11ARM64.cmd" 1 file(s) copied.

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Details for image : C:\WOR\Win11_ARM64_WIM\Src\boot.wim

Index : 1 Name : Microsoft Windows PE (arm64) Description : Microsoft Windows PE (arm64) Size : 2,293,849,261 bytes

Index : 2 Name : Microsoft Windows Setup (arm64) Description : Microsoft Windows Setup (arm64) Size : 2,412,052,618 bytes

The operation completed successfully.

Waiting for 0 seconds, press a key to continue ...

*** Mount boot.wim index 1

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Mounting image [==========================100.0%==========================] The operation completed successfully.

*** Inject ARM64 device drivers

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Image Version: 10.0.22621.2861

Searching for driver packages to install...

Error: 2

No driver packages were found on the specified path. Verify that the driver .INF files are in the specified location and try the command again.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

*** Replace stornvme.sys and storahci.sys in boot.wim index 1

SUCCESS: The file (or folder): "C:\WOR\Win11_ARM64_WIM\mWIM\Windows\system32\drivers\stornvme.sys" now owned by user "AzureAD\JohnPoindexter". processed file: C:\WOR\Win11_ARM64_WIM\mWIM\Windows\system32\drivers\stornvme.sys Successfully processed 1 files; Failed processing 0 files C:\WOR\Win11_ARM64_WIM\stornvme_storahci\stornvme.pdb C:\WOR\Win11_ARM64_WIM\stornvme_storahci\stornvme.sys 2 file(s) copied.

SUCCESS: The file (or folder): "C:\WOR\Win11_ARM64_WIM\mWIM\Windows\system32\drivers\storahci.sys" now owned by user "AzureAD\JohnPoindexter". processed file: C:\WOR\Win11_ARM64_WIM\mWIM\Windows\system32\drivers\storahci.sys Successfully processed 1 files; Failed processing 0 files C:\WOR\Win11_ARM64_WIM\stornvme_storahci\storahci.pdb C:\WOR\Win11_ARM64_WIM\stornvme_storahci\storahci.sys C:\WOR\Win11_ARM64_WIM\stornvme_storahci\storahci.zip 3 file(s) copied.

*** Unmount boot.wim

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully.

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Details for image : C:\WOR\Win11_ARM64_WIM\Src\boot.wim

Index : 1 Name : Microsoft Windows PE (arm64) Description : Microsoft Windows PE (arm64) Size : 2,294,285,320 bytes

Index : 2 Name : Microsoft Windows Setup (arm64) Description : Microsoft Windows Setup (arm64) Size : 2,412,052,618 bytes

The operation completed successfully.

*** Mount boot.wim index 2

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Mounting image [==========================100.0%==========================] The operation completed successfully.

*** Inject ARM64 device drivers

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Image Version: 10.0.22621.2861

Searching for driver packages to install...

Error: 2

No driver packages were found on the specified path. Verify that the driver .INF files are in the specified location and try the command again.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

*** Replace stornvme.sys and storahci.sys in boot.wim index 2

SUCCESS: The file (or folder): "C:\WOR\Win11_ARM64_WIM\mWIM\Windows\system32\drivers\stornvme.sys" now owned by user "AzureAD\JohnPoindexter". processed file: C:\WOR\Win11_ARM64_WIM\mWIM\Windows\system32\drivers\stornvme.sys Successfully processed 1 files; Failed processing 0 files C:\WOR\Win11_ARM64_WIM\stornvme_storahci\stornvme.pdb C:\WOR\Win11_ARM64_WIM\stornvme_storahci\stornvme.sys 2 file(s) copied.

SUCCESS: The file (or folder): "C:\WOR\Win11_ARM64_WIM\mWIM\Windows\system32\drivers\storahci.sys" now owned by user "AzureAD\JohnPoindexter". processed file: C:\WOR\Win11_ARM64_WIM\mWIM\Windows\system32\drivers\storahci.sys Successfully processed 1 files; Failed processing 0 files C:\WOR\Win11_ARM64_WIM\stornvme_storahci\storahci.pdb C:\WOR\Win11_ARM64_WIM\stornvme_storahci\storahci.sys C:\WOR\Win11_ARM64_WIM\stornvme_storahci\storahci.zip 3 file(s) copied.

*** Unmount boot.wim

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully.

*** Export install.wim

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Exporting image [==========================100.0%==========================] The operation completed successfully.

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Details for image : C:\WOR\Win11_ARM64_WIM\Src\install_Pro.wim

Index : 1 Name : Windows 11 Pro Description : Windows 11 Pro Size : 22,513,517,969 bytes

The operation completed successfully.

Waiting for 0 seconds, press a key to continue ...

*** Mount install.wim

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Error: 11

An attempt was made to load a program with an incorrect format.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

*** Inject ARM64 device drivers

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Error: 2

Unable to access the image. Make sure that the image path and the Windows directory for the image exist and you have Read permissions on the folder.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

*** Mount WinRE WIM

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Error: 3

The system cannot find the path specified.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

*** Inject ARM64 device drivers

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Error: 2

Unable to access the image. Make sure that the image path and the Windows directory for the image exist and you have Read permissions on the folder.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

*** Unmount WinRE WIM

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Error: 50

The request is not supported.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

*** Replace stornvme.sys and storahci.sys in install.wim ERROR: The system cannot find the path specified. C:\WOR\Win11_ARM64_WIM\mWIM\Windows\system32\drivers\stornvme.sys: The system cannot find the path specified. Successfully processed 0 files; Failed processing 1 files The system cannot find the path specified. C:\WOR\Win11_ARM64_WIM\stornvme_storahci\stornvme.pdb The system cannot find the path specified. 0 file(s) copied. ERROR: The system cannot find the path specified. C:\WOR\Win11_ARM64_WIM\mWIM\Windows\system32\drivers\storahci.sys: The system cannot find the path specified. Successfully processed 0 files; Failed processing 1 files The system cannot find the path specified. C:\WOR\Win11_ARM64_WIM\stornvme_storahci\storahci.pdb The system cannot find the path specified. 0 file(s) copied.

*** Unmount install.wim

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Error: 50

The request is not supported.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

*** Export install.wim

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Exporting image [==========================100.0%==========================] The operation completed successfully.

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Details for image : C:\WOR\Win11_ARM64_WIM\Src\install_Pro_Cleaned.wim

Index : 1 Name : Windows 11 Pro Description : Windows 11 Pro Size : 22,513,517,969 bytes

The operation completed successfully.

Done!

C:\Windows\System32>

[schau80269]

The script failed to process install.wim. Mounting of install.wim failed with Error:11 and it went downhill from there.

Were you trying to get Win11 OS installed into the same NVMe SSD that was loaded by WoR-Flasher with the modified installation files? I don't recommend doing this as it is more likely to have issues. Instead, use a 8/16GB USB flash drive (not a NVMe SSD in a USB enclosure!) and get WoR-Flasher to load this up, then copy out the boot.wim & install.wim files to another PC to run the script, then copy the modified files (in the Src subfolder) back into the USB flash drive (boot.wim in BOOT partition sources subfolder, install.wim in the exFAT partition) overwriting the originals. Install a blank NVMe SSD to m.2 Hat as OS installation target drive.

Attached is an updated script. Since there are no ARM64 device drivers for RPi5 to inject, simply remove the Drivers subfolder (or don't create one) and the script should skip all driver injections and only do the stornvme driver replacement. Even storahci replacement is not needed for RPi5. So the stornvme_storahci subfolder should just have 2 files: the v6 stornvme.sys & stornvme.pdb and nothing else. This is a better way to install Win11, as the USB flash drive can be used repeatedly for OS installs after WoR-Flasher and script processing is done once.

If you use NVMe SSD in USB enclosure with Realtek RTL9210B bridge chip as OS installation target, your installations will continue to be unsuccessful. I wasted several days fighting this last month and concluded that Win11 ARM64 OS has a major incompatibility with that Realtek chip with no fix in sight. You are much better off installing OS directly into NVMe SSD attached to m,2 Hat. My script was written to enable this to work.

One more thing: Don't leave a copy of the script sitting in the installation media. WoR-Flasher seems to pick it up which may mess up the Pre-installation environment.

Script_to_Inject_ARM64_Drivers_Replace_stornvme_for RPi5_Win11ARM64.zip

[SeaDog58]

Well I tried again with failure trying to load Windows Pro 11 on to a 256g NVME drive in a m.2 Hat. The attachments are extracts showing the errors in your CMD script and the associated errors in the DISM log. I don’t know whether those are critical.

For the original install.wim and boot.wim I have been using those found in the WOR Flasher Files folder on the RPI 5 Raspbian desktop. These files were created weeks ago before I started messing with NVME drives when I first tried WOR Flasher. In your instructions are a little unclear. You say “…then copy the modified files (in the Src subfolder) back into the USB flash drive (boot.wim in BOOT partition sources subfolder, install.wim in the exFAT partition)…” Shouldn’t the modified files go back into the WOR Flasher Files folder? For the creation of the NVME in the m.2 Hat running the Flasher from Raspbian, I don’t see the USB flash drive involved.

John

From: schau80269 @.> Sent: Friday, July 5, 2024 9:42 PM To: Botspot/wor-flasher @.> Cc: SeaDog58 @.>; Author @.> Subject: Re: [Botspot/wor-flasher] Problem Using WOR-Flasher (Issue #158)

The script failed to process install.wim. Mounting of install.wim failed with Error:11 and it went downhill from there.

Were you trying to get Win11 OS installed into the same NVMe SSD that was loaded by WoR-Flasher with the modified installation files? I don't recommend doing this as it is more likely to have issues. Instead, use a 8/16GB USB flash drive (not a NVMe SSD in a USB enclosure!) and get WoR-Flasher to load this up, then copy out the boot.wim & install.wim files to another PC to run the script, then copy the modified files (in the Src subfolder) back into the USB flash drive (boot.wim in BOOT partition sources subfolder, install.wim in the exFAT partition) overwriting the originals. Install a blank NVMe SSD to m.2 Hat as OS installation target drive.

Attached is an updated script. Since there are no ARM64 device drivers for RPi5 to inject, simply remove the Drivers subfolder (or don't create one) and the script should skip all driver injections and only do the stornvme driver replacement. Even storahci replacement is not needed for RPi5. So the stornvme_storahci subfolder should just have 2 files: the v6 stornvme.sys & stornvme.pdb and nothing else. This is a better way to install Win11, as the USB flash drive can be used repeatedly for OS installs after WoR-Flasher and script processing is done once.

If you use NVMe SSD in USB enclosure with Realtek RTL9210B bridge chip as OS installation target, your installations will continue to be unsuccessful. I wasted several days fighting this last month and concluded that Win11 ARM64 OS has a major incompatibility with that Realtek chip with no fix in sight. You are much better off installing OS directly into NVMe SSD attached to m,2 Hat. My script was written to enable this to work.

One more thing: Don't leave a copy of the script sitting in the installation media. WoR-Flasher seems to pick it up which may mess up the Pre-installation environment.

Script_to_Inject_ARM64_Drivers_Replace_stornvme_for RPi5_Win11ARM64.ziphttps://github.com/user-attachments/files/16114586/Script_to_Inject_ARM64_Drivers_Replace_stornvme_for.RPi5_Win11ARM64.zip

— Reply to this email directly, view it on GitHubhttps://github.com/Botspot/wor-flasher/issues/158#issuecomment-2211570906, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGHY4P5FIHASQXIK7JP3QNDZK5DODAVCNFSM6AAAAABIPQGL5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJRGU3TAOJQGY. You are receiving this because you authored the thread.Message ID: @.**@.>>

CMD Script Results with Errors. All steps before and after this were completed successfully.

*** Mount install.wim

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Error: 11

An attempt was made to load a program with an incorrect format.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

*** Mount WinRE WIM

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Error: 3

The system cannot find the path specified.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

*** Unmount WinRE WIM

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Error: 50

The request is not supported.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

*** Replace stornvme.sys in install.wim ERROR: The system cannot find the path specified. H:\Win11_ARM64_WIM\mWIM\Windows\system32\drivers\stornvme.sys: The system cannot find the path specified. Successfully processed 0 files; Failed processing 1 files The system cannot find the path specified. H:\Win11_ARM64_WIM\stornvme_storahci\stornvme.pdb The system cannot find the path specified. 0 file(s) copied.

*** Replace storahci.sys in install.wim ERROR: The system cannot find the path specified. H:\Win11_ARM64_WIM\mWIM\Windows\system32\drivers\storahci.sys: The system cannot find the path specified. Successfully processed 0 files; Failed processing 1 files The system cannot find the path specified. H:\Win11_ARM64_WIM\stornvme_storahci\storahci.pdb The system cannot find the path specified. 0 file(s) copied.

*** Unmount install.wim

Deployment Image Servicing and Management tool Version: 10.0.22621.2792

Error: 50

The request is not supported.

The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log

* 2024-07-06 10:26:00, Warning DISM DISM WIM Provider: PID=40756 [ReadWimHeader:(1906) -> header version mismatch] H:\Win11_ARM64_WIM\Src\install_Pro.wim (HRESULT=0x8007000B) - CWimManager::WimProviderMsgLogCallback [40756.33612] [0xc144012e] 2024-07-06 10:26:00, Error DISM DISM WIM Provider: PID=40756 [WIMCreateFile:(419) -> Fail to read WIM header] H:\Win11_ARM64_WIM\Src\install_Pro.wim (HRESULT=0x8007000B) - CWimManager::WimProviderMsgLogCallback 2024-07-06 10:26:00, Error DISM DISM WIM Provider: PID=40756 TID=33612 "WIM open failed." - CWimImageInfo::Mount(hr:0x8007000b) 2024-07-06 10:26:00, Error DISM DISM Imaging Provider: PID=40756 TID=33612 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:833 - CGenericImagingManager::InternalOpMount(hr:0x8007000b) 2024-07-06 10:26:00, Error DISM DISM Imaging Provider: PID=40756 TID=33612 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:746 - CGenericImagingManager::InternalCmdMount(hr:0x8007000b) 2024-07-06 10:26:00, Error DISM DISM Imaging Provider: PID=40756 TID=33612 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:538 - CGenericImagingManager::ExecuteCmdLine(hr:0x8007000b) 2024-07-06 10:26:00, Info DISM DISM.EXE: Image session has been closed. Reboot required=no. 2024-07-06 10:26:00, Info DISM DISM.EXE: 2024-07-06 10:26:00, Info DISM DISM.EXE: <----- Ending Dism.exe session -----> 2024-07-06 10:26:00, Info DISM DISM.EXE: 2024-07-06 10:26:00, Info DISM PID=4456 TID=41804 Scratch directory set to 'C:\Users\JOHNPO~1\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir 2024-07-06 10:26:00, Info DISM PID=4456 TID=41804 DismCore.dll version: 10.0.22621.1 - CDISMManager::FinalConstruct 2024-07-06 10:26:00, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log 2024-07-06 10:26:00, Info DISM PID=4456 TID=41804 Successfully loaded the ImageSession at "C:\WINDOWS\system32\Dism" - CDISMManager::LoadLocalImageSession 2024-07-06 10:26:00, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log 2024-07-06 10:26:00, Info DISM DISM Provider Store: PID=4456 TID=41804 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger 2024-07-06 10:26:00, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log 2024-07-06 10:26:00, Info DISM DISM Manager: PID=4456 TID=41804 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession 2024-07-06 10:26:00, Info DISM DISM.EXE: 2024-07-06 10:26:00, Info DISM DISM.EXE: <----- Starting Dism.exe session -----> 2024-07-06 10:26:00, Info DISM DISM.EXE: 2024-07-06 10:26:00, Info DISM DISM.EXE: Host machine information: OS Version=10.0.22631, Running architecture=amd64, Number of processors=16 2024-07-06 10:26:00, Info DISM DISM.EXE: Dism.exe version: 10.0.22621.2792 2024-07-06 10:26:00, Info DISM DISM.EXE: Executing command line: C:\WINDOWS\system32\Dism /Mount-Image /ImageFile:H:\Win11_ARM64_WIM\mWIM\windows\system32\recovery\winre.wim /Index:1 /mountDir:H:\Win11_ARM64_WIM\winre_mWIM 2024-07-06 10:26:00, Info DISM DISM Imaging Provider: PID=4456 TID=41804 WIM image specified - CGenericImagingManager::GetImageInfoCollection 2024-07-06 10:26:00, Error DISM DISM WIM Provider: PID=4456 "WIM open failed." - CWimImageInfoCollection::Initialize(hr:0x80070003) 2024-07-06 10:26:00, Error DISM DISM WIM Provider: PID=4456 onecore\base\ntsetup\opktools\dism\providers\wimprovider\dll\wimimageinfocollection.cpp:73 - CWimImageInfoCollection::CreateWimImageInfoCollection(hr:0x80070003) 2024-07-06 10:26:00, Error DISM DISM WIM Provider: PID=4456 TID=41804 Failed to create the image info collection. - CWimManager::GetImageInfoCollection(hr:0x80070003) 2024-07-06 10:26:00, Error DISM DISM Imaging Provider: PID=4456 TID=41804 "Call into specific imaging provider failed for GetImageInfoCollection." - CGenericImagingManager::GetImageInfoCollection(hr:0x80070003) 2024-07-06 10:26:00, Error DISM DISM Imaging Provider: PID=4456 TID=41804 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:930 - CGenericImagingManager::InternalOpGetImageByIndex(hr:0x80070003) 2024-07-06 10:26:00, Error DISM DISM Imaging Provider: PID=4456 TID=41804 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:773 - CGenericImagingManager::InternalOpMount(hr:0x80070003) 2024-07-06 10:26:00, Error DISM DISM Imaging Provider: PID=4456 TID=41804 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:746 - CGenericImagingManager::InternalCmdMount(hr:0x80070003) 2024-07-06 10:26:00, Error DISM DISM Imaging Provider: PID=4456 TID=41804 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:538 - CGenericImagingManager::ExecuteCmdLine(hr:0x80070003) 2024-07-06 10:26:00, Info DISM DISM.EXE: Image session has been closed. Reboot required=no. 2024-07-06 10:26:00, Info DISM DISM.EXE: 2024-07-06 10:26:00, Info DISM DISM.EXE: <----- Ending Dism.exe session -----> 2024-07-06 10:26:00, Info DISM DISM.EXE: 2024-07-06 10:26:00, Info DISM PID=33720 TID=33836 Scratch directory set to 'C:\Users\JOHNPO~1\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir 2024-07-06 10:26:00, Info DISM PID=33720 TID=33836 DismCore.dll version: 10.0.22621.1 - CDISMManager::FinalConstruct 2024-07-06 10:26:00, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log 2024-07-06 10:26:00, Info DISM PID=33720 TID=33836 Successfully loaded the ImageSession at "C:\WINDOWS\system32\Dism" - CDISMManager::LoadLocalImageSession 2024-07-06 10:26:00, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log 2024-07-06 10:26:00, Info DISM DISM Provider Store: PID=33720 TID=33836 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger 2024-07-06 10:26:00, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log 2024-07-06 10:26:00, Info DISM DISM Manager: PID=33720 TID=33836 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession 2024-07-06 10:26:00, Info DISM DISM.EXE: 2024-07-06 10:26:00, Info DISM DISM.EXE: <----- Starting Dism.exe session -----> 2024-07-06 10:26:00, Info DISM DISM.EXE: 2024-07-06 10:26:00, Info DISM DISM.EXE: Host machine information: OS Version=10.0.22631, Running architecture=amd64, Number of processors=16 2024-07-06 10:26:00, Info DISM DISM.EXE: Dism.exe version: 10.0.22621.2792 2024-07-06 10:26:00, Info DISM DISM.EXE: Executing command line: C:\WINDOWS\system32\Dism /Unmount-Image /mountDir:H:\Win11_ARM64_WIM\winre_mWIM /Commit 2024-07-06 10:26:00, Info DISM DISM FFU Provider: PID=33720 TID=33836 [H:\Win11_ARM64_WIM\winre_mWIM] is not recognized by the DISM FFU provider. - CFfuImage::Initialize 2024-07-06 10:26:00, Info DISM DISM Imaging Provider: PID=33720 TID=33836 The provider FfuManager does not support CreateDismImage on H:\Win11_ARM64_WIM\winre_mWIM - CGenericImagingManager::CreateDismImage 2024-07-06 10:26:00, Info DISM DISM VHD Provider: PID=33720 TID=33836 [H:\Win11_ARM64_WIM\winre_mWIM] is not recognized by the DISM VHD provider. - CVhdImage::Initialize 2024-07-06 10:26:00, Info DISM DISM Imaging Provider: PID=33720 TID=33836 The provider VHDManager does not support CreateDismImage on H:\Win11_ARM64_WIM\winre_mWIM - CGenericImagingManager::CreateDismImage [33720.33836] [0x80070002] FIOReadFileIntoBuffer:(1456): The system cannot find the file specified. [33720.33836] [0xc142011c] UnmarshallImageHandleFromDirectory:(641) [33720.33836] [0xc142011c] WIMGetMountedImageHandle:(2910) 2024-07-06 10:26:00, Info DISM DISM WIM Provider: PID=33720 TID=33836 [H:\Win11_ARM64_WIM\winre_mWIM] is not a WIM mount point. - CWimMountedImageInfo::Initialize 2024-07-06 10:26:00, Info DISM DISM Imaging Provider: PID=33720 TID=33836 The provider WimManager does not support CreateDismImage on H:\Win11_ARM64_WIM\winre_mWIM - CGenericImagingManager::CreateDismImage 2024-07-06 10:26:00, Info DISM DISM Imaging Provider: PID=33720 TID=33836 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage 2024-07-06 10:26:00, Error DISM DISM Imaging Provider: PID=33720 TID=33836 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:1081 - CGenericImagingManager::InternalCmdUnmount(hr:0x80070032) 2024-07-06 10:26:00, Error DISM DISM Imaging Provider: PID=33720 TID=33836 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:538 - CGenericImagingManager::ExecuteCmdLine(hr:0x80070032) 2024-07-06 10:26:00, Info DISM DISM.EXE: Image session has been closed. Reboot required=no. 2024-07-06 10:26:00, Info DISM DISM.EXE: 2024-07-06 10:26:00, Info DISM DISM.EXE: <----- Ending Dism.exe session -----> 2024-07-06 10:26:00, Info DISM DISM.EXE: 2024-07-06 10:26:00, Info DISM PID=39880 TID=38068 Scratch directory set to 'C:\Users\JOHNPO~1\AppData\Local\Temp\'. - CDISMManager::put_ScratchDir 2024-07-06 10:26:00, Info DISM PID=39880 TID=38068 DismCore.dll version: 10.0.22621.1 - CDISMManager::FinalConstruct 2024-07-06 10:26:00, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log 2024-07-06 10:26:00, Info DISM PID=39880 TID=38068 Successfully loaded the ImageSession at "C:\WINDOWS\system32\Dism" - CDISMManager::LoadLocalImageSession 2024-07-06 10:26:00, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log 2024-07-06 10:26:00, Info DISM DISM Provider Store: PID=39880 TID=38068 Found and Initialized the DISM Logger. - CDISMProviderStore::Internal_InitializeLogger 2024-07-06 10:26:00, Info DISM Initialized Panther logging at C:\WINDOWS\Logs\DISM\dism.log 2024-07-06 10:26:00, Info DISM DISM Manager: PID=39880 TID=38068 Successfully created the local image session and provider store. - CDISMManager::CreateLocalImageSession 2024-07-06 10:26:00, Info DISM DISM.EXE: 2024-07-06 10:26:00, Info DISM DISM.EXE: <----- Starting Dism.exe session -----> 2024-07-06 10:26:00, Info DISM DISM.EXE: 2024-07-06 10:26:00, Info DISM DISM.EXE: Host machine information: OS Version=10.0.22631, Running architecture=amd64, Number of processors=16 2024-07-06 10:26:00, Info DISM DISM.EXE: Dism.exe version: 10.0.22621.2792 2024-07-06 10:26:00, Info DISM DISM.EXE: Executing command line: C:\WINDOWS\system32\Dism /Unmount-Image /mountDir:H:\Win11_ARM64_WIM\mWIM /Commit 2024-07-06 10:26:00, Info DISM DISM FFU Provider: PID=39880 TID=38068 [H:\Win11_ARM64_WIM\mWIM] is not recognized by the DISM FFU provider. - CFfuImage::Initialize 2024-07-06 10:26:00, Info DISM DISM Imaging Provider: PID=39880 TID=38068 The provider FfuManager does not support CreateDismImage on H:\Win11_ARM64_WIM\mWIM - CGenericImagingManager::CreateDismImage 2024-07-06 10:26:00, Info DISM DISM VHD Provider: PID=39880 TID=38068 [H:\Win11_ARM64_WIM\mWIM] is not recognized by the DISM VHD provider. - CVhdImage::Initialize 2024-07-06 10:26:00, Info DISM DISM Imaging Provider: PID=39880 TID=38068 The provider VHDManager does not support CreateDismImage on H:\Win11_ARM64_WIM\mWIM - CGenericImagingManager::CreateDismImage [39880.38068] [0x80070002] FIOReadFileIntoBuffer:(1456): The system cannot find the file specified. [39880.38068] [0xc142011c] UnmarshallImageHandleFromDirectory:(641) [39880.38068] [0xc142011c] WIMGetMountedImageHandle:(2910) 2024-07-06 10:26:00, Info DISM DISM WIM Provider: PID=39880 TID=38068 [H:\Win11_ARM64_WIM\mWIM] is not a WIM mount point. - CWimMountedImageInfo::Initialize 2024-07-06 10:26:00, Info DISM DISM Imaging Provider: PID=39880 TID=38068 The provider WimManager does not support CreateDismImage on H:\Win11_ARM64_WIM\mWIM - CGenericImagingManager::CreateDismImage 2024-07-06 10:26:00, Info DISM DISM Imaging Provider: PID=39880 TID=38068 No imaging provider supported CreateDismImage for this path - CGenericImagingManager::CreateDismImage 2024-07-06 10:26:00, Error DISM DISM Imaging Provider: PID=39880 TID=38068 onecore\base\ntsetup\opktools\dism\providers\imagingprovider\dll\genericimagingmanager.cpp:1081 -

[schau80269]

Something is not right about your install.wim, and DISM chokes up trying to mount it, so of course the stornvme driver replacement fails. Your installation media was thus not prepared properly to support OS installation into NVMe SSD. The script must be run from an elevated command prompt. I suggest you start over by downloading a recent Win11 24H2 ARM64 build from uupdump.net. I've had great success with the 26100.1000 ARM64 build. Attached is a procedure I just wrote up. There are steps to be done with both x86-64 Win11 PC and Raspberry Pi 5. I strongly recommend you use a dedicated USB3 8/16GB flash drive to be OS installation media. Once prepared properly, this USB flash drive should be usable repeatedly for installing OS.

Windows_11_ARM64_OS_Installation_into_NVMe_SSD_for_Raspberry_Pi_5.zip

[SeaDog58]

Thanks for the detailed instructions. I will start fresh this week. John

From: schau80269 @.> Sent: Sunday, July 7, 2024 8:03 PM To: Botspot/wor-flasher @.> Cc: SeaDog58 @.>; Author @.> Subject: Re: [Botspot/wor-flasher] Problem Using WOR-Flasher (Issue #158)

Something is not right about your install.wim, and DISM chokes up trying to mount it, so of course the stornvme driver replacement fails. Your installation media was thus not prepared properly to support OS installation into NVMe SSD. The script must be run from an elevated command prompt. I suggest you start over by downloading a recent Win11 24H2 ARM64 build from uupdump.net. I've had great success with the 26100.1000 ARM64 build. Attached is a procedure I just wrote up. There are steps to be done with both x86-64 Win11 PC and Raspberry Pi 5. I strongly recommend you use a dedicated USB3 8/16GB flash drive to be OS installation media. Once prepared properly, this USB flash drive should be usable repeatedly for installing OS.

Windows_11_ARM64_OS_Installation_into_NVMe_SSD_for_Raspberry_Pi_5.ziphttps://github.com/user-attachments/files/16121345/Windows_11_ARM64_OS_Installation_into_NVMe_SSD_for_Raspberry_Pi_5.zip

— Reply to this email directly, view it on GitHubhttps://github.com/Botspot/wor-flasher/issues/158#issuecomment-2212628863, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGHY4P6EC6AZXU5QGI4O4YLZLHJLZAVCNFSM6AAAAABIPQGL5GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMJSGYZDQOBWGM. You are receiving this because you authored the thread.Message ID: @.**@.>>