DISM offline source

Hello @dbdan22,
Welcome to TenForums.

dbdan22 said:

I'd like to prepare an offline source for DISM from the good system for repairing the bad one.

By offline, I mean no windows update and no network. Just take the files I need from the good system, plunk them onto a flash drive, and repair the bad system, pointing to the flash drive with dism /source, completely offline.

- What files do I need from the good system to prepare the source?

- What is the DISM syntax, and what is the easiest method: WIM, ESD or something else?

I already have a bootable Win 10 flash drive made with Rufus from the Microsoft ISO, same build. Can I use that? But wouldn't the bad system be at a higher patch level than the flash drive because it was exposed to Windows Update? is there a way to update the flash drive to current patch level? Or does it make a difference?

You are talking about repairing a Windows Image, either Offline or Online.

[1] You might find these useful for the different DISM commands and what they perform . . .

> Repair a Windows Image
> How to Repair Windows 10 Image using DISM

[2] The above is referring to performing an In-Place-Upgrade - Repair Install. Here is a brief overview that I have put together . . .

 In-Place-Upgrade - Repair Install

Information & Tutorials:

This is a Non-Destructive Process which keeps ALL your Apps, Programs, and Personal Data etc Intact . . .

IMPORTANT: This is an extract from the Tutorial below . . .

• You will only be able to do a repair install of Windows 10 from within Windows 10. You will not be able to do a repair install at boot or in Safe Mode.
  
• You will need at least around 10 GB + what Windows is currently using of free space available on the Windows drive.
• The installation media (ex: ISO or USB) must be the same edition and same or newer build as your currently installed Windows 10. If it's not, then the repair install will fail.
• The installation media (ex: ISO or USB) must be the same base language (aka: system default language) as your currently installed Windows 10. If it's not, then you will not keep anything.
• If you have a 32-bit Windows 10, then you must use a 32-bit ISO or USB.
• If you have a 64-bit Windows 10, then you must use a 64-bit ISO or USB.

> How to Do a Repair Install of Windows 10 with an In-place Upgrade

Basically . . .

[1] Download the ISO to the Desktop.
[2] Right-click the ISO > Mount.
[3] Open File Explorer.
[4] Double-click the Mounted Drive to open it.
[5] Double-click setup.exe.
[6] Choose the Upgrade option.
[7] Select Change what to keep.
[8] Select One of the following . . .

• Keep Personal Files and Apps.
• Keep Personal Files Only.
• Nothing.

[9] Unmount the ISO by right-clicking the Mounted Drive > Eject.

The only downside is that you could POSSIBLY lose some of your personalizations.

Recommendations:

DISABLE:

ANY Non-Microsoft . . .

• Antivirus Software.
• Firewall software.
• Drive Encryption Software.

---

I hope this helps.

1) Create a bootable iso of latest Windows system (Rufus is a good tool and get latest iso from UUPDUMP
2) Boot the windows install (note we are NOT going to install Windows !!) on the GOOD computer
3) Choose Repair computer (note also we aren't going to REPAIR the computer
4) get into command mode
5) now run the DISM capture-image command capturing the image from your computer, and directing it to any device. Run the DISM from the drive "X" note : that's the the one you booted into via command mode.

You dont need to do all that.

Your running system can be captured into a wim using one of several tools, e.g. the command line tool wimlib, or using dism++ which has a nice gui. Dism++10.1.1000.100.zip

Very easy

File>Save Image




If it is the running os, the vss box is automatically ticked and the description, etc is autofilled.

Just browse to the destination and give the wim a name. E.G in the pic below it is D:\Backup.wim

Then click ok



Advanced users can go to settings and organize exclusions. For the geeks, wimlib is faster at capturing than ms dism or dism++

Dan,

dbdan22 said:

Well, yes, but I've already got a Rufus flash, and I'd rather get the image offline. Y'know when you're trying to get some work done and all of a sudden TrustedInstaller fires up and grabs 25% CPU and you never really know what it's up to? Better to grab an offline image when it's not mucking around with it.....

I had never even considered Dism as a method for transferring between computers before. Now that you have done / are about to do this for the first time, could you spare a moment to share some words of wisdom with me?

1 I'd be grateful for your full Dism command as an example. I've found some guidance in Dism's built-in Help & in MSDocs but a real-word example would be welcome.
2 Did your source & target computers have exactly the same hardware? If not, did Windows cope alright with the difference? I have my drivers backed up ready to re-install straightaway but, once again, your experiences would be valuable.
3 Both my source & target computers have relocated user folders but both have exactly the same relocations [e.g. Documents -> E:\Documents on both of them]. Did your task involve anything comparable?
4 I routinely make system images of both computers. Are you aware of any particular advantage to using Dism to effect the transfer rather than using conventional system imaging & restoring between them?

I would also be grateful for answers to the questions I'm too stupid to think of asking you.

My intended target is a 'new' computer that I set up for its primary task upon delivery last Summer but I have never got round to installing & setting up all my other applications [which would match those on my main computer however I did the job]. So I'd have a proper motivation for the task instead of just doing it as an exercise.

TIA,
Denis

OK, thanks. Actually, it was the Dism Capture-Image syntax you used that I thought would be a useful example for me.

Denis