In our own network environment, some foreign websites are not allowed to visit. Clicking on the first link says that this page cannot be accessed, the other two are accessible.
"the other two are accessible.". Well, any one is OK. You want its method, not image. 1 is enough, 2 is garbage.
I want to understand what an Unstaged Image is,so that I can make a standard Unstaged Image。(照葫芦画个瓢,哈哈)
Regular image - Store - Language features - Feafure on demand = standard Unstaged Image (barebone system) i.e. Unstaged ISO --> install packages defined in Edition mum (and Editions to be upgraded to, if applicable) --> barebone system (standard Unstaged Image) No Store NO Language features NO Feafure on demand
It seems that I still misunderstood Unstaged Image, this is the image I made, and I also think this is Unstaged Image.All packages are in a staging state. . Spoiler
No, it is not. 19041.1.191206-1406.VB_RELEASE_CLIENTUNSTAGED_RETAIL_X64FRE_EN-US.ISO\sources\install.wim\ Code: Packages Users Windows
It seem unstaged Image Structure is very different from normal image. What is the big advantages of Unstage ?
Excuse me, what is the difference between this method and offline installation of xxx.mum (such as Professional.mum) with Apply-Unattend? I find it easier to install xxx.mum with Apply-Unattend.
Use unattend to add edition and langpack; Use dism to add fods Add .NET native images and appxs Modify image state
1. .NET native images, copied, won't work. It needs ngen eqi. https://forums.mydigitallife.net/th...struction-project.80939/page-347#post-1726809 2. image state modification won't help. Still have to iso boot\install. [About Install method] Normal image: ISO boot and Partition boot (and accepts unattend.xml.) Unstaged image: ISO boot only (because it has not been generalized. If Partition boot, it won't get to OOBE. And Unstaged image won't accept unattend.xml.)
I remember unstaged image can accept unattend AS LONG AS image state is modified , unless I got it wrong