Windows 10: Upgrade for Win 8.1 Update WIMBoot Installations to Win 10

Do we know what will happen with users who have a WIMBoot Installation (aka compressed) installation of Windows 8.1 Update on their system?

Will they get the update like the others or will they have to create their own Windows 10 WIMBootinstallation?

edit: typo

:)

 

Windows 10 upgrade will affect my recovery partition?

my original windows before upgrade was win 8.1 wimBoot version

so If I format drive C and install a win 8.1 wimBoot version on it,

will my reset factory option of my tablet(ASUS T200) work again or not?

windows.old folder is deleted and I can't simply go back to win 8.1 with options available in windows 10

 

Enabling reset factory windows 10 with downgrading to original win 8.1(after 30day limit)

I recently have upgrade my Asus T200 tablet win 8.1 to windows 10

cause the windows.old folder is deleted I can't use the easy Go back to previous OS 8.1 option in windows 10

nor that I have a backup or image of my win 8.1

0.I plan to install a WIMBoot win 8.1 32bit so that reset factory of my tablet may work again

1.the only thing I have is the 8 GB recovery partition of my tablet which is not shown in my compter when windows is running.

I have used reset factory in win 8.1 many times but since I have upgraded to windows 10 that option is not available

0.my only clue is that if I Install a wimboot version of windows 8.1 on the drive C ,the recovery option may work again.

2.previously I tried installing win 8.1 on drive C bot the recovery option in startup of my ASUS T200 failed.so I wonder if a wimboot version of windows 8.1 do the trick.

0.....this trick may apply to other tablets that their recovery partition is useless after upgrading to windows 10.(if it works!!!)

3.so does anybody know why my recovery option didn't work with installing a normal win 8.1 (not a WIMBoot)

4.and is it possible that upgrading to windows 10 affected the recovery partition in anyway like deleting some files from it?

(normally acessing that partition from my computer is not possible without labeling and formatting that recovery partition)

and last question.

5.strangely when I go from windows 10 installation USB in customize option

drivers are shown as a 100 MB and a

300 MB and 20 GB drive C plus 8 GB recovery partition.it shows that 8GB recovery partition is encrypted and has 500 MB used apace.

5.x.seriously is the image of my factory win 8.1 is just 500 MB or is it just because the drive is encrypted!

I thought something like a 7GB image file is in that recovery partition that when ever I do a factory reset it is used.

Enabling reset factory windows 10 with downgrading to original OS 8.1(after 30day limit)

I recently have upgrade my Asus T200 tablet win 8.1 to windows 10

cause the windows.old folder is deleted I can't use the easy Go back to previous OS 8.1 option in windows 10

nor that I have a backup or image of my win 8.1

0.I plan to install a WIMBoot win 8.1 32bit so that reset factory of my tablet may work again

1.the only thing I have is the 8 GB recovery partition of my tablet which is not shown in my compter when windows is running.

I have used reset factory in win 8.1 many times but since I have upgraded to windows 10 that option is not available

0.my only clue is that if I Install a wimboot version of windows 8.1 on the drive C ,the recovery option may work again.

2.previously I tried installing win 8.1 on drive C bot the recovery option in startup of my ASUS T200 failed.so I wonder if a wimboot version of windows 8.1 do the trick.

0.....this trick may apply to other tablets that their recovery partition is useless after upgrading to windows 10.(if it works!!!)

3.so does anybody know why my recovery option didn't work with installing a normal win 8.1 (not a WIMBoot)

4.and is it possible that upgrading to windows 10 affected the recovery partition in anyway like deleting some files from it?

(normally acessing that partition from my computer is not possible without labeling and formatting that recovery partition)

and last question.

5.strangely when I go from windows 10 installation USB in customize option

drivers are shown as a 100 MB and a

300 MB and 20 GB drive C plus 8 GB recovery partition.it shows that 8GB recovery partition is encrypted and has 500 MB used apace.

5.x.seriously is the image of my factory win 8.1 is just 500 MB or is it just because the drive is encrypted!

I thought something like a 7GB image file is in that recovery partition that when ever I do a factory reset it is used.

 

I get the impression from this Twitter exchange that, as of early May, it was supposed to work but it wasn't exactly working smoothly (if you click on the link and look at the replies).
Tweet



— Twitter API (@user) date

 

I was saying I found this

https://blogs.windows.com/bloggingwi...act-footprint/

 

They're still weighing they options but I went through a WMIboot deployment and it is a tedious process but now it looks like you'd install in <32 GB devices just as you normally would and Windows will detect this device class and start self-compressing. That's what I take away from that blog.

 

I am marking this a s solved and add a an upgrade experience that I'd like to share:

On my HP Stream 11, I had Win 8.1 WIM Boot when I got it. After the Windows 10 upgrade, the Push Button partition was gone and I had basically the entire 32 GB for the Windows partition (growing from 21 GB to 28 GB) .

Windows 8.1 WIM Boot (before)




Windows 10 Home (after)




Is WIM Boot dead then? It is still there in the Windows 10 build of DISM:

 

I think WIMBoot is 'deprecated' - the command will still be there (which for one thing means you can still use the same version of DISM to work with Windows 8.1), but it isn't the preferred route for Windows 10.

If you go to an elevated command prompt, and type this command, what does it say?:
Code: compact /compactos:query[/quote] I'd expect it to say 'The system is in the compact state'

I believe that instead of WIMBoot, in Windows 10 there are two technologies for compression:

• Compact OS (as per the command I mentioned above) - which is about the OS
• 'Single-instancing' your applications, so that applications are run from a 'Provisioning Package' which has been created for use with Reset and Recovery Drives

The compactOS setting should be determined automatically when you install. When I tried to upgrade my tablet it set the CompactOS flag as expected, but when I tried a clean-install later, probably because it was missing some key drivers, it didn't figure out that it could compact it. However I think you can switch it on and off with these commands:
Code: compact /CompactOs:always[/quote] or
Code: compact /CompactOs:never[/quote] The single-instancing of applications is done with DISM, and I have to admit I've not been brave enough to try it yet. I don't think it happens automatically when you upgrade from 8.1 to 10.

I'm also not sure whether you can do it on a running installation or if it needs to be done before first use. I know how to create a Provisioning Package but it's not clear to me if "DISM /Apply-CustomDataImage" creates a new Provisioning Package itself or if I need to create it first. Also I'm not sure how it works when you subsequently update applications (eg. applications like Firefox frequently update themselves), if they are stored in a .ppkg file.

I'll get round to doing some playing with single-instancing in a Virtual Machine at some point.

Further reading if you're interested:
Compact OS, single-instancing, and image optimization
How Windows 10 achieves its compact footprint

 

I think the same happened here. I upgraded, then re-installed from scratch and now apparently have an uncompressed OS.

This is strange because Windows takes about half of the drive *Smile which is 32 GB, immediately post-install. After a year of updates or so, go figure. Either Setup is not very good at determining whether compression is needed or it concluded that the eMMC drive is too slow for compression? ("Windows is able to assess if a device can use compression without reducing human-perceivable responsiveness.")

I'll still have to look into Provisioning Packaging and Single Instancing. Very informative!

 

Apparently it was not possible earlier releases
Microsoft Explains OS Compression in Windows 10 - Thurrott.com

But from what this guy says here it works now.
WIMBoot and Windows 10

I am trying to confirm if this is so now. Can someone verify that this works now?

 

I've installed compressed Windows 10 on two computers now with 32 GB eMMC memories - one NextBook tablet and an Azulle Stick computer with no issues:

Important precautions to take before upgrading to Windows 10 - Windows 10 Forums

When Windows setup detects the limited memory for installation, it will automatically install in the compressed state. You can also enable the compressed state on any computer:

Windows 10 Feature Focus: CompactOS

 

Thanks for the insightful response. How much space does one save with the CompactOS feature? What pros & cons in terms of overhead/ performance on a system?