Micro 10 Boot Wim

Micro 10 Boot Wim With EFI Support:

boot wim weighs 99.6 MB

Should work with Windows 10 Pro, Pro N, Home & Home N Editions.

Extract EFI.rar and place your install.wim or install.esd in the source folder and generate your new iso.


[You must be registered and logged in to see this link.]



Micro 10 Boot Wim No EFI Support:

boot wim weighs 93.5 MB

Should work with Windows 10 Pro, Pro N, Home & Home N Editions.

Extract bios.rar and place your install.wim or install.esd in the source folder and generate your new iso.


[You must be registered and logged in to see this link.]

Hi mackyreddy ,

as i found that your boot.wim has no uefi support like the site you shared four Micro 10 Pro OS .
Why do you remove uefi support ?
is it to trim down the OS ? or any other reason ?

Thanks.......................

UEFI doesn't take much space hardly four files in boot wim around 10 MB and four files in install wim again around 10 MB.

No one requested me to keep the feature, so i removed.

I personally use EFI and made boot wim for myself as i use hackintosh Big Sur as dual boot.

no worries i will also upload a new boot wim with EFI support .

uploaded new boot wim with EFI support, also added support for Vmware Workstation Player & Virtualbox.

cheers

Thank you very much

can you also included "lang.ini" and "setup.exe" files, because without those files the installation may be NOT WORK

 thanks have a great day and stay safe.
 _________________
 home7ech
 pS : Creative Learning by Doing, Slowly but Do iT Cool's

Hi mackyreddy

Thank You very much ? You gave me some hints

So I removed  c:\Windows\SystemApps completedly from my running System
and everything seems ok
The big problem is to remove
StartMenuExperienceHost.exe
resources.pri
StartUI.dll
in C:\Windows\SystemApps\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\

I deleted those  by booting in a second Windows O.S
I Used every trick  to delete them from the running Windows with no results
SystemApps Directory with all the dorectories inside is completedly removed and everything seems OK up to now

Do You or Winterstorm have any idea to delete them the normal way as this is cheating

icy

icy007 wrote:

Hi mackyreddy

Thank You very much ? You gave me some hints

So I removed  c:\Windows\SystemApps completedly from my running System
and everything seems ok
The big problem is to remove
StartMenuExperienceHost.exe
resources.pri
StartUI.dll
in C:\Windows\SystemApps\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\

I deleted those  by booting in a second Windows O.S
I Used every trick  to delete them from the running Windows with no results
SystemApps Directory with all the dorectories inside is completedly removed and everything seems OK up to now

Do You or Winterstorm have any idea to delete them the normal way as this is cheating

icy

Well we can't delete all System Apps as few apps are part of Windows Shell.

Required Apps for smooth functioning of OS:

1. Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy as the name suggests it is required for Start Menu

2. Microsoft.Windows.Search_cw5n1h2txyewy for Windows Search

3. ShellExperienceHost_cw5n1h2txyewy is required for Taskbar & System Tray

4. Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy can be deleted only if you are using unattended.xml with Administrator as user, if you want to name your PC better don't delete it as it breaks oobe.

Other System Apps can be deleted.

home7ech wrote:

can you also included "lang.ini" and "setup.exe" files, because without those files the installation may be NOT WORK

 thanks have a great day and stay safe.
 _________________
 home7ech
 pS : Creative Learning by Doing, Slowly but Do iT Cool's

yes what you said is wright, setup.exe inside the boot.wim is different from your Windows folder, So boot.wim doesn't work with other windows source folder.

I will upload the entire Folder, just place your install.wim or install.esd in the source folder and generate the iso.

regards

Hi mackyreddy

All those are removed and everything works perfect,
At the moment of writing i am using this Window Operating system
without the C:WindowsSystemApps directory and all the directories inside it
So it is possible , the culprit is to remove
StartMenuExperienceHost.exe
resources.pri
StartUI.dll
in C:WindowsSystemAppsMicrosoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy
in an easy way, they seem to be protected  in a way rhat  TrustedInstaller can not remove,
it is only possible by cheating

icy


Hi mackyreddy
I have no install.wim or install.esd   of it,
I did it just in an running Windows  as test ,
This can not be done  this way as  a few hunderd registry items are removed
and what is inside
c:\Windows\SystemApps\Microsoft.AccountsControl_cw5n1h2txyewy\
c:\Windows\SystemApps\Microsoft.AsyncTextService_8wekyb3d8bbwe\
c:\Windows\SystemApps\microsoft.creddialoghost_cw5n1h2txyewy\
c:\Windows\SystemApps\Microsoft.Windows.CloudExperienceHost_cw5n1h2txyewy\
c:\Windows\SystemApps\Microsoft.Windows.FileExplorer_cw5n1h2txyewy\
c:\Windows\SystemApps\Microsoft.Windows.OOBENetworkConnectionFlow_cw5n1h2txyewy\
c:\Windows\SystemApps\Microsoft.Windows.Search_cw5n1h2txyewy\
c:\Windows\SystemApps\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\
c:\Windows\SystemApps\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\
c:\Windows\SystemApps\MicrosoftWindows.UndockedDevKit_cw5n1h2txyewy\
c:\Windows\SystemApps\NcsiUwpApp_8wekyb3d8bbwe\

StartMenuExperienceHost.exe
& resources.pri
& StartUI.dll
in C:\Windows\SystemApps\Microsoft.Windows.StartMenuExperienceHost_cw5n1h2txyewy\
are the problem to remove an easy way
There must be something with higher righrs than TrustedInstaller

icy


icy

updated first post with Windows installation folder structure along with boot wim, you should place your own install.wim or install.esd in the source folder and generate your new iso.

cheers

may i suggested, is more easy for you to updated or modified the uploaded files (link) if not in the compressed format (just in folder)

 thanks have a great day and stay safe.
 _________________
 home7ech
 pS : Creative Learning by Doing, Slowly but Do iT Cool's

Hi 
Removing C:WindowsSystemApps and al directories do not give any prpblems until now
Browser ,VPN , Netflix,Tv via internet,Total Commander install programs,
uninstall programs, audio, everything working
In my opinion code in this directory and  subdirectories  controls a lot of thing 
inside Windows and should be removed , mayby with Winreducer.
Everything seems to go quicker and shutdown is also quicker.
icy

Hi
Thank You all for the comments
I could remove  c:\Windows\SystemApps\ and all directories and files inside  in my running Windows,
Everything is ok,Windows runs perfectly without those
icy

i have tested with Windows 10 v1709 build 16299.2107.x86fre_rs3 and get error



as far as i know if used "boot.wim" from Windows 10 x86-bit based system it work for All-in-One (AiO) Windows x86/x64 bit based system.

 regard and stay safe.
 _________________
 home7ech
 pS : Creative Learning by Doing, Slowly but Do iT Cool's

Thanks for sharing this mackyreddy ! I have one issue, I was able to create a working bootable and installable windows USB drive, But I noticed using your pre-made boot.wim setup, during installation it creates a 529 MB recovery partition on the installation hard drive with windows 10 build 2004(20H1) and 2009(20H2), and If I was to install those builds of windows using the stock MSDN iso, or a winreducer built iso, it would only create a 100 MB and a 16 MB parition, not the recovery partition. (it seems that recovery partition was abandoned since build 20H1 during installation)

Do you know if it would be possible to create your boot.wim and environment without that partition being created? It's an awesome wimfile you made, but it would be nice to keep the half GB of storage

I found something sweet out as far as a space saving build is concerned! I created a winreduced iso built from windows 20H1, swapped in a winreduced install.wim from 19H1, and it installed windows without the half GB recovery partition being created! Normally any windows installation that is build 19H2 (1909) or older creates the partition automatically during installation. Great way to save a half GB of space if you want to use an older build of windows!

What are you trying to do, create a boot.wim ("PE") that runs like a tiny windows 10 system? I used to do that with windows 7, there is an entire forum, complete with special supporting software dedicated to that called "winbuilder", if I remember right.

The links don't work, someone who has the files and can send them to me, grateful.