Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account


Sysprep before adding drivers via DISM

  • Please log in to reply
1 reply to this topic


  • Member
  • 4 posts
  • Joined 15-February 08
Hello all,
I am trying to figure out the correct way to add all my supported models drivers into my image.
It appears to work if i add them via dism before sysprep but that seems like a pain. I tried adding them after i syspreped and it gave errors.

How to remove advertisement from MSFN




  • Member
  • 41 posts
  • Joined 25-February 08
I haven't tried doing it after sysprep myself, but why do you say adding them with DISM is a pain? Seeing as you can add any number of drivers (and patches while you're at it) in one fell swoop thanks to the possibility of recursing all the folders, I'm not sure why you refer it as a pain to do so.

I'm still in the "early" stages of developping an image for my department, but one thing I've done a LOT is having to recreate the .WIM file from scratch a lot, because of too much tampering and errors on my part. I've got 2 big folders; 1 for drivers & 1 for patches/other packages and with 2 DISM commands (/add-package & /add-driver) over 20 items get added in no time recursively.

Hopefully, it's just that you don't know of the /recurse switch, like me back then (lack of documentation for that switch). If that's not the case, I've never tried to add drivers after sysprep, so can't help you there.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users