DISM - Add or Remove Drivers on an Offline Image  

Page 5 of 5 FirstFirst ... 345
  1.    #40

    techquest,

    That error message is referencing an image. You need to run that command against the folder to which you copied the contents of the image on the hard drive or SSD.

    To summarize:

    You should be copying the contents of a Windows 10 ISO image or DVD to a folder on the hard drive. Then run the attrib command referencing that folder.

    As an example, suppose you have a Windows 10 ISO image. Right-click the image and choose mount. Go to the drive letter that the image is mounted as, select all the files and copy them to a location on the hard disk. Use that folder to perform all further operations. In fact, you can right click the drive letter that the ISO image was mounted to and select eject at this point since you don't need it any longer.

    Apologies if that is already what you are doing. It's just that it sounds like you are working on the image rather than the files copied from that image.
      My ComputerSystem Spec

  2.    #41

    hsehestedt said: View Post
    techquest,

    That error message is referencing an image. You need to run that command against the folder to which you copied the contents of the image on the hard drive or SSD.

    To summarize:

    You should be copying the contents of a Windows 10 ISO image or DVD to a folder on the hard drive. Then run the attrib command referencing that folder.

    As an example, suppose you have a Windows 10 ISO image. Right-click the image and choose mount. Go to the drive letter that the image is mounted as, select all the files and copy them to a location on the hard disk. Use that folder to perform all further operations. In fact, you can right click the drive letter that the ISO image was mounted to and select eject at this point since you don't need it any longer.

    Apologies if that is already what you are doing. It's just that it sounds like you are working on the image rather than the files copied from that image.

    Thanks, no apologies needed as you never know, but I can confirm I was working on the correct copied files in the correct folder. I also thought, just to be sure it wasn't anything to do with the external ssd, of going through everything again using a partition on the same drive as C: , so I did but sadly the same result as before. So now I'm going to try Kari's suggested repair install as there seems to be nowhere else to go at this point. As said earlier I will let you guys know how it goes after the event.

    - - - Updated - - -

    Decided to do clean install W10 1903 so back up and operational now.



    This is why I've got a smile and thought you would want to know after all the efforts that have gone into this, it's gold:


    :\WINDOWS\system32> DISM /Mount-image /imagefile:N:\ISO_Files\sources\install.wim /Index:3 /MountDir:N:\Mount
    Deployment Image Servicing and Management tool
    Version: 10.0.18362.1

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



    Thanks to you both for your efforts and I have enjoyed working with you and the learning curve that stuff like this moves me through. Will be playing The Star Spangled Banner tonight for sure, Hendrix style (Woodstock) and Whitney Houston (Super Bowl XXV) if that's okay with you, sorry Kari but it will be with a bottle of good old JD rather than a SM.
      My ComputerSystem Spec

  3.    #42

    W10 1903, 'eh? Just be careful with that - it's entirely possible that a new ADK will be released once 1903 is actually finalized in May.

    It's good to see that Microsoft is leaving it with Windows Insiders for further testing for a good while this time to hopefully catch any major bugs before release. 1809 was not a good initial release.

    In any case, glad to hear that it is working for you.

    I have a question for you:

    I have written a program that completely automates certain processes such as adding all the latest Windows updates into a Windows image. Actually, it can update as many images as you want all automatically. I'm currently working on writing the code to automate the whole process of adding drivers to Windows images as well. Would you be interested in trying this out when I have completed it?
      My ComputerSystem Spec

  4.    #43

    hsehestedt said: View Post
    W10 1903, 'eh? Just be careful with that - it's entirely possible that a new ADK will be released once 1903 is actually finalized in May.

    Been using it in Hyper V for a while now without any real issues, slow ring, so thought I would try it out for real and see how it goes. If it turns out to be a problem then I will just do another new install of 1809, which again I didn't have any real issues with, until the beginning of this thread.

    It's good to see that Microsoft is leaving it with Windows Insiders for further testing for a good while this time to hopefully catch any major bugs before release. 1809 was not a good initial release.

    In any case, glad to hear that it is working for you.

    I have a question for you:

    I have written a program that completely automates certain processes such as adding all the latest Windows updates into a Windows image. Actually, it can update as many images as you want all automatically. I'm currently working on writing the code to automate the whole process of adding drivers to Windows images as well. Would you be interested in trying this out when I have completed it?
    On your question, sounds good to me as updates and drivers always seem to be the most lengthily processes. So when your ready just PM and we can take it from there, if I can help you by trying it out that's fine by me.
      My ComputerSystem Spec

  5. Kari's Avatar
    Posts : 15,803
    Windows 10 Pro
    Thread Starter
       #44

    hsehestedt said: View Post
    W10 1903, 'eh? Just be careful with that - it's entirely possible that a new ADK will be released once 1903 is actually finalized in May.
    Just a personal opinion: I recommend always using the latest ADK Insider Preview, currently build 18362: Download Windows Insider Preview ADK

    This way, you always have the absolute latest ADK.

    Kari
      My ComputerSystem Spec

  6.    #45

    Kari said: View Post
    Just a personal opinion: I recommend always using the latest ADK Insider Preview, currently build 18362: Download Windows Insider Preview ADK

    This way, you always have the absolute latest ADK.

    Kari
    Thanks Kari will take a look at that tomorrow going to take the rest of the night off and chill some. Have a good weekend.

    - - - Updated - - -

    Just when all seemed to be going well!

    I went through the rest of the tut with no issues with drivers cmdlet

    dism /Image:N:\Mount /Add-Driver /Driver:N:\XPS_Drivers /Recurse

    100% successful

    save when I got to 5.1, using the following cmdlet:

    dism /Unmount-Image /MountDir:N:\Mount /Commit

    100% successful.

    The problem is N:Mount is empty! Just to be sure I went through the process 3 times, same result each time. Why would this be, I thought the changes would all be saved as the tut suggests. So what went wrong, any suggestions please?
      My ComputerSystem Spec

  7. Kari's Avatar
    Posts : 15,803
    Windows 10 Pro
    Thread Starter
       #46

    techquest said: View Post
    The problem is N:Mount is empty! Just to be sure I went through the process 3 times, same result each time. Why would this be, I thought the changes would all be saved as the tut suggests. So what went wrong, any suggestions please?
    Of course the Mount folder is empty after you have committed (saved) the changes to WIM image!

    The Mount folder is just a temporary folder containing the mounted WIM, a Windows image. You mount install.wim to this temporary folder, meaning it will be unpacked. You service it, like adding drivers, then commit (save) the changes. This means that the changes will be written to your WIM image file.

    Mount folder is just a temporary storage location. It should be empty before you mount a WIM file, it will be empty after you unmount it.

    When dismounting, Mount folder will always be emptied. That is how it should be. The drivers you added are now included in your install.wim file.

    Kari
      My ComputerSystem Spec

  8.    #47

    Kari said: View Post
    Of course the Mount folder is empty after you have committed (saved) the changes to WIM image!

    The Mount folder is just a temporary folder containing the mounted WIM, a Windows image. You mount install.wim to this temporary folder, meaning it will be unpacked. You service it, like adding drivers, then commit (save) the changes. This means that the changes will be written to your WIM image file.

    Mount folder is just a temporary storage location. It should be empty before you mount a WIM file, it will be empty after you unmount it.

    When dismounting, Mount folder will always be emptied. That is how it should be. The drivers you added are now included in your install.wim file.




    Kari

    Thanks for the explanation Kari , having looked at the wim file now I can see that it has grown by about 1.1GB and didn't realize that the 15GB (80 drivers) would be compressed to that extent when being put into the wim file, and I missed the resized wim, guess I should have thought about it before the post. Oh well we live and learn.
      My ComputerSystem Spec


 
Page 5 of 5 FirstFirst ... 345

Tutorial Categories

DISM - Add or Remove Drivers on an Offline Image Tutorial Index Network & Sharing Instalation and Upgrade Browsers and Email General Tips Gaming Customization Apps and Features Virtualization BSOD System Security User Accounts Hardware and Drivers Updates and Activation Backup and Restore Performance and Maintenance Mixed Reality Phone


Related Threads
Performance & Maintenance Use DISM to Repair Windows 10 Image in Tutorials
How to Repair Windows 10 Image using DISM If a Windows image becomes unserviceable, you can use the Deployment Imaging and Servicing Management (DISM) tool to update the files and correct the problem. For example, you would use DISM to fix...
Servicing an offline image, mounting an image, committing changes, it all sounds a bit complicated to an average Windows user. However, it's just geek speak meaning modifying default Windows install image, the install.wim file. It is a straight...
SFC Scannow or DISM/RestoreHealth using Image in Performance & Maintenance
Windows 10 user. Having some trouble with my system after coming back from a weekend. Nothing major...just having trouble playing some games that require plugins etc Regardless if it's related, I just wanted to run an SFC/Scannow or...
Hi I installed Windows ADK 10 v1511 on Windows 10 v1511 Enterprise 64 bit. I typed the following commands: Dism /Apply-Image /ImageFile:"<wim_File_Path>\install.wim" /Index:1 /ApplyDir:"<Apply_Directory_Path>" /Verify /CheckIntegrity...
Hello I have a laptop that I took the HDD out of and connected it to another Windows 10 machine. I ran the command Dism /Image:e:\ /Cleanup-Image /RestoreHealth but get the error Deployment Image Servicing and Management tool Version:...
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

Designer Media Ltd
All times are GMT -5. The time now is 19:15.
Find Us