Mr. Strat Posted July 20, 2016 Report post Posted July 20, 2016 Using Server 2012 R2 to deploy Windows 10 Pro and I'm unable to inject the Ethernet driver for a newer computer into boot.wim. I've tried using the WDS snap-in and the dism command line. It keeps telling me I need a newer version of dism - but I'm using MDT 2013 Update 2. Any help appreciated Quote Share this post Link to post Share on other sites More sharing options...
0 thadkew Posted July 20, 2016 Report post Posted July 20, 2016 You downloaded the latest Windows ADK and got the DISM that came with it? Quote Share this post Link to post Share on other sites More sharing options...
0 nate@tamu Posted July 28, 2016 Report post Posted July 28, 2016 I'm having the same problem, and to add a little more information that may help Mr. Strait, it seems that my system is using a DISM version in WDS that is older than the one installed with the windows 10 ADK. This is a brand new installation of Server 2012r2, all updates, and the latest ADK from Microsoft. If I use the DISM located in Program Files (x86)\10\Assessment and Deployment Kit\Deployment Tools\dism, I get Version 10.0.10586.0, but if I use the version located at C:\windows\system32 (the one I suspect WDS uses), I get version 6.3.9600.17031. I'll start another thread with this question, but if anyone knows how to make WDS use a different instance of DISM or to update to the newest version in System32, I'd be more than grateful. Nate Quote Share this post Link to post Share on other sites More sharing options...
Using Server 2012 R2 to deploy Windows 10 Pro and I'm unable to inject the Ethernet driver for a newer computer into boot.wim.
I've tried using the WDS snap-in and the dism command line. It keeps telling me I need a newer version of dism - but I'm using MDT 2013 Update 2.
Any help appreciated
Share this post
Link to post
Share on other sites