wimlib

Posted: **Tue Nov 10, 2015 10:09 am**

Hi,

I had a similar issue with Versions 1.8.1 and 1.8.2.
Images were produced with DISM (I dont know which version since the files were supplied by someone else) and applied with wimlib 1.8.0 or earlier on an 3.18 linux kernel with ntfs-3g (1:2012.1.15AR.5-2.1+deb7u2). Which worked fine

After switching to a 4.0.4-1 Kernel with ntfs-3g 1:2014.2.15AR.2-1+deb8u2 and an newly compiled wimlib (both ver. 1.8.1 and 1.8.2) the produced windows partitions would boot up to an BOD (Stop 7b - Inaccessible Boot device) due to missing Drivers.

The same Image applied in the same environment with your provided wimlib Beta 1.8.3 worked just fine.

So long story short. I think you fixed the issue and thank you for doing it so promptly. (imagine a *ThumpsUp* Emoticon right here)

-tobias

Posted: **Wed Nov 11, 2015 2:00 am**

Great! I'll probably be officially releasing v1.8.3 within a week or two; then fewer people will run into this problem. It's been a little delayed due to other changes.

Posted: **Sat Nov 14, 2015 8:21 pm**

Fixed in wimlib v1.8.3.

Posted: **Sun Nov 15, 2015 1:40 am**

synchronicity wrote:Fixed in wimlib v1.8.3.

Thanks again for your work on this.

wimlib

[SOLVED] Issue w wimlib 1.8.1 and later (deploying Win7)

Re: [SOLVED] Issue w wimlib 1.8.1 and later (deploying Win7)

Re: [SOLVED] Issue w wimlib 1.8.1 and later (deploying Win7)

Re: [SOLVED] Issue w wimlib 1.8.1 and later (deploying Win7)

Re: [SOLVED] Issue w wimlib 1.8.1 and later (deploying Win7)