When I try to boot my uefi client from LAN it successfully downloads boot.wim from my WDS 2012, shows the Windows Logo for some seconds, but then it crashes, showing BSOD and the message "UNMOUNTABLE_BOOT_VOLUME". I'm using the same x64 boot.wim as with the BIOS clients, but with the mbr clients it does work. What is it, that makes my boot.wim unusable for uefi clients?
Asked
Active
Viewed 1,053 times
0
-
Some questions come to mind: Do you have enough RAM on the clients to boot the x64 image, how did you build the boot image? – Elliot Huffman Jun 09 '15 at 14:20
-
8gb RAM, the boot.wim comes from a windows 8.1 DVD - the same boot.wim works when I switch the client from uefi to legacy mode. I used the same boot.wim to build a WinPE USB Stick. When I boot from that stick, I can start the install, but installation fails becaus of missing drivers. But the image seems to be mountable however... – woodrapp Jun 10 '15 at 05:59
-
Ok, what drivers are missing? Also is your bios/uefi up to date? Are you able to uefi boot other computers? – Elliot Huffman Jun 10 '15 at 15:46
-
I injected all the drivers I could find into my boot.wim and I also installed latest bios update but no avail. I can install the same uefi client with a dvd and that works. – woodrapp Jun 15 '15 at 11:11
-
I tried the following: I made a WinPE bootable USB-Stick with ADK 8.1, booted my PC from that stick in UEFI mode, and it worked. Then I took the boot.wim from my WinPE Stick and loaded it as an additional boot image on WDS. When I pxe-boot my UEFI client from that boot.wim coming from adk, I get the unmountable_boot_volume error again. Then I thought, maybe some drivers are missing, and I injected all the device drivers I could find into my boot.wim, but that would not make a difference. – woodrapp Jun 15 '15 at 13:02
-
Did you try using a different computer (different hardware set)? – Elliot Huffman Jun 15 '15 at 16:21
-
Yes I did, but only HP. Notebook, Desktop, SSD, HD. – woodrapp Jun 16 '15 at 11:26
-
Did the same thing happen to the notebook and desktop? – Elliot Huffman Jun 16 '15 at 19:39
-
What are you trying to deploy? – Elliot Huffman Jun 16 '15 at 19:40
-
same thing happens with nb and dt, with ssd and hdd. trying to deploy windows 8.1 x64 – woodrapp Jun 17 '15 at 11:24
-
Have you tried using mdt, did you check the hashes for the source install disk and did you try using the driver feature of wds? Some of these questions are also like suggestions for better practices if you generally do not follow them... – Elliot Huffman Jun 17 '15 at 13:38
-
I just tried it with mdt and got the same result. Everything works no problem as soon as I switch the client to bios. – woodrapp Jun 18 '15 at 11:32
-
Have you considered booting with BIOS then deploying a UEFI configuration? Can you get to the boot loader menu in UEFI mode? Is Secure Boot enabled? – Elliot Huffman Jun 18 '15 at 17:28
-
I tried pxe booting in bios mode and deploying the uefi stuff - this does not work. When I try to pxe boot in uefi i can select the boot loader. bsod appears after succesful download of boot.wim secure boot is not enabled – woodrapp Jun 19 '15 at 12:23
-
When you say `this does not work` are you referring to the deployment type? If so then it is possible. Try to add more images to the BIOS loader and see if you can get a selectable menu. – Elliot Huffman Jun 19 '15 at 13:32
-
I added different boot.wims but no avail. Could it be there is something wrong with the .bcd which is generated by the wds-server? – woodrapp Jun 23 '15 at 07:03
-
That is a good idea, See if you can regenerate the BCD files. Tell me how it goes. – Elliot Huffman Jun 23 '15 at 12:33