Jump to content

Mini 10x64 in VHD


wimb

Recommended Posts

2 hours ago, wimb said:

Stop at step 6 is wrong.

Ok. I went that far and asked you as I was getting confused how to do next steps. 

2 hours ago, wimb said:

Then Windows is not installed at all and besides the VHD remains mounted as drive Y: 

Well, it was mounted by previous, so I have mount and dismount few times and same issue with Error Message. 

2 hours ago, wimb said:

For VHD_WIMBOOT prg the VHD must be unmounted

Even with unmounted I am getting same error message. 

2 hours ago, wimb said:

which would have occurred if you did at least step 9 but it is better to follow all steps of page 2

Ok. But I am a bit confused on how to execute each of these next steps before hitting VHD WIM BOOT. (Is there any video?) 

7. BOOTICEx64.exe from Upper Right Icon - BCD of current system file Z:\efi\microsoft\boot - Professional mode - BootMenuPolicy = Legacy

// PS: Did you see the images I shared above as I have done some small differences/ changes. 

// This is just adding Boot Entry for the existing VHD from Step 6? Right?  -

// I have used EasyBCD and BCDBoot.exe before... A bit confused by BOOTICE. .

How exactly and where to add the Step 7? - Video? 

8. Option needed for RAMDISK SVBus driver - In BootIce Use R-mouse to create New element - AllowPrereleaseSignatures - Yes

// I have no idea how and where to do this?  

9. Reboot and install Win10x64 in VHD with Offline Local Account - Connect to LAN or WLAN for Install of missing Drivers and Activation

// Win 10 was already applied by WinNTSetup (I've used DISM /apply from WIM methods before) to VHD right? Booting via the Step 7 boot entry will just do a FIRST BOOT and SETUP - Right?

Once all this is over.. shut it down? Then COMPACT using the VHD WIM BOOT app with VHD ... UNMOUNTED? 

How to make sure it finds it instead of getting lost and pop the error message? 

PS: Lots of thanks. Grazi! 

Edited by crashnburn4u
Link to comment
Share on other sites


On 9/16/2021 at 6:55 PM, wimb said:

In that case:

1. WinNTSetup according to step 2-6 of page 2 as you did already

2. VHD_WIMBOOT - Capture WimBoot LZX and Apply in Compact LZX mode in Fixed VHD 10 or 15 GB - Offline Windows

This second step saves a lot of space and creates the Boot entries on Selected Boot Drive - Nothing more to do

- Always use the supplied Firewall App Blocker and Enable WhiteList to Allow Internet Browser only

- This is the easiest way to block unwanted internet traffic including Windows Update and prevents the growth of Used Size inside VHD

 

On 9/17/2021 at 5:09 PM, wimb said:

Stop at step 6 is wrong. Then Windows is not installed at all and besides the VHD remains mounted as drive Y: 

For VHD_WIMBOOT prg the VHD must be unmounted which would have occurred if you did at least step 9 but it is better to follow all steps of page 2

In VHD_WIMBOOT you can Select VHD file After select of System Drive (often drive C: where Wimboot folder with Captured WIM file and VHD file are located)

Then the Capture button can be used .....

 

I think the following things were done correctly, except a few differences of items from Page 2. Can you see what was wrong/ and what next? 

Now what on Page 3 Steps would be relevant to me? 

FYI all details: 

http://reboot.pro/index.php?showtopic=22323&page=4#entry219437 

Edited by crashnburn4u
Link to comment
Share on other sites

Quote

1. WinNTSetup - Fresh Install in 25 GB Fixed VHD located on internal SSD / Harddisk using Win10x64 ISO from TechBench - use page 2
- Select Boot drive (usually EFI drive Z:) and VHD is mounted as Drive Y: - Unattended Install - for Local Account - select to Add Drivers folder

2. VHD_WIMBOOT - Capture WimBoot LZX and Apply in Compact LZX mode in Fixed VHD 10 GB - Offline Windows

Only above is relevant to you for Compact mode Install and you don't need page 3 which is for WimBoot mode Install

Where and on what type of drive is your VHD located ?

What type of VHD did you create ?

Did you succeed in booting Windows in 25 GB VHD using WinNTSetup ? (according to step 1, elaborated on page 2)

Did you succeed in booting Windows in 10 GB VHD using VHD_WIMBOOT ? (according to step 2)

Where and How do you fail ? What Error Message ?

Give ScreenShot of Windows Disk Management showing disks and drives.

Edited by wimb
Link to comment
Share on other sites

@wimb, would you please point me to a link where it explains in detail what exactly that Win_Reduce_Trusted does? In an early post you state that it is "suitable to Reduce Windows 7/8/10 x64", and I'm interested it in using it for install applications other than VHD installations, primarily for Windows 7 and 8. If it wouldn't be directly applicable for such use, I could at least use it as an example to model from. TIA.

Cheers and Regards

Link to comment
Share on other sites

19 hours ago, bphlpt said:

@wimb, would you please point me to a link where it explains in detail what exactly that Win_Reduce_Trusted does?

In folder Win_Reduce_Trusted-43\Win_reduce\File_List you find files that for each category describe the files to keep (SysWOW64 and WindowsApps) or remove (all other categories)

base_winsxs_2.cmd of cdob is used to reduce WinSxS folder

Win_Reduce_Trusted can be used to reduce Windows installed in partition, but Windows must be offline e.g. by booting with PE or other Windows

More Info post #1 and #2 and in VHD_WIMBOOT PDF

Edited by wimb
Link to comment
Share on other sites

  • 1 month later...

Update Win_Reduce_Trusted-48

Download:  from wimb GitHub  -  Win_Reduce_Trusted-48

Download File E = Encrypted PassWord = bootwimb

Manual:   VHD_WIMBOOT.pdf   - Download:  Win10_21H2 x64 ISO  and  Win11 ISO from Microsoft

- Edge is removed  - Portable FireFox or MaxthonPortable can be used as VHD External  Portable Internet Browser

  To Enable Edge you need to adjust remove_sub_Prog_x86.txt and remove_sub_Users.txt - make leading ; to disable removal

- WindowsApps ScreenSketch is enabled to make Editable ScreenShots

Mini-10x64 version 21H2 VHD has Compact LZX UsedSize 1.46 GB (running OS = 1.63 GB) with LZX WIM Size = 1.15 GB

My old Mini-10x64 of january 2021 has 24276 files and LZX UsedSize = 1.97 GB and  LZX WIM = 1.62 GB

Download File_List  - Mini_10x64_21H2.zip

Mini_10x64_21H2 has   18.806 Files and   3.031 Folders

Full   10x64  21H2 has 115.304 Files and 32.333 Folders 

23745912_Mini_10x64_VHD_WinApps_2021-11-18060956.png.4076934be6153d15ce59a202fc0f5bcb.png   Mini_10x64_VHD_RAMDISK_2021-11-18.thumb.jpg.82ab9d5102a60e411e03234360f43cc5.jpg

Edited by wimb
Link to comment
Share on other sites

Update Win_Reduce_Trusted-50

Download:  from wimb GitHub  -  Win_Reduce_Trusted-50

Download File E = Encrypted PassWord = bootwimb

Manual:   VHD_WIMBOOT.pdf   - Download:  Win10_21H2 x64 ISO  and  Win11 ISO from Microsoft

- Added Windows Update Blocker - Wub folder in \Add_Folders_Files\Port_Apps folder of Win_reduce
- Shortcut on Desktop to launch Wub_x64.exe added in \Add_to_UserPath\Desktop folder
- Shortcut on Desktop to launch Network - ncpa.cpl - Easy Switch On / Off Network Adapter
- PS.exe is running now as Admin so that all apps in PStart Menu are Running as Admin
- Added Run_System_Info_x64.exe in \Add_to_UserPath\Desktop folder
  Run_System_Info_x64.exe will Find and Run \System_Info\System_Info_x64.exe on Any Drive

  For this purpose your System_Info-53 folder must be in Root of Any Drive and must be Renamed as System_Info

First time you need to boot Mini-10x64.vhd as FILEDISK and be sure there is No Network Connection possible.
Then you need on Desktop launch Wub_x64.exe to Disable Windows Update and Protect this Setting.

It is now safe to connect to Network using Enable WhiteList Off setting in Firewall App Blocker.

Boot Mini-10x64.vhd as FILEDISK or from RAMDISK and
Connect to Internet and FireFox pages appear OK without an increase of the Mini-10x64 UsedSize

Mini-10x64_2021-11-24_144508.thumb.jpg.050eec39c6570ec435e0d7ddff2aaa1a.jpg   Win_Reduce_2021-11-25_191305.jpg.39a3c962b880e954798f790c69d727fe.jpg

Mini-10x64_2021-11-26_102921.thumb.jpg.b3d2a122d3f364e11b6d6e8e69d77635.jpg

Edited by wimb
Link to comment
Share on other sites

  • 4 weeks later...

Download:  from wimb GitHub  -  Win_Debloat-28  and   Win_Reduce_Trusted-52  -   :cheerleader: 

Download File E = Encrypted PassWord = bootwimb

Manual:   VHD_WIMBOOT.pdf   - Download:  Win10_21H2 x64 ISO  and  Win11 ISO from Microsoft

Preferred is to use Win10x64 as Normal Operating System with Defender and AV Software Disabled
- Allows Easy Mount / UnMount of VHD and Prevents Attacks on SVBus Driver
- Otherwise use Win10XPE as Norwal working OS so that there is no problem with Defender attacking SVBus driver

1. WinNTSetup do Fresh Install of Win10x64 in VHD for Local Account - Take care that Internet Cable is Disconnected - Page 1-2 of Manual and Settings
2. Boot with VHD and Run Win_Debloat_x64.exe - Debloat Online Windows and Install SVBus Driver
3. Reboot VHD first as FILEDISK from Boot Manager Menu - to make Install of SVBus driver effective
    in Windows Boot Manager Menu Requires F8 Disable driver signature enforcement needed for SVBus Driver
4. Boot other Win10x64 OS - Mount VHD by Double Click - Run Win_Reduce_Trusted.cmd - Reduce Offline Windows
5. UnMount VHD by Eject - use R-Mouse on VHD Drive in Windows Explorer
6. Use VHD_WIMBOOT_Trusted.cmd for Capture and Apply of WIM file in New Mini-10x64.vhd Size 2.5 GB
7. Boot Mini-10x64 VHD from RAMDISK - Connect first time to Internet using Potable FireFox - All changes in OS are volatile
    Booting from RAMDISK - Use Steps 6-10 on page 1 of Manual VHD_WIMBOOT PDF

Thanks to: 
W4RH4WK Debloat PowerShell scripts
Windows Update Blocker from Sordum
PowerRun from Sordum
schtrom for making SVBus Virtual SCSI Host Adapter for GRUB4DOS
Best Answer

- Several times Press Enter key (First Click on OneDrive Remove Window) to let the Program Win_Debloat_x64 Continue
- it allows to view intermediate results and give instructions on How to Install Manually SVBus driver

Windows Update Blocked and Defender Disabled, 51 Tasks and 67 Services are Disabled, WindowsApps Removed with Clean Start Menu
OneDrive Removed, Telemetry Blocked, SVBus Driver Installed for booting from RAMDISK, UsedSize Reduced to below 2 GB for Mini-10x64 OS in VHD

Win_Debloat_2021-12-16_155422.jpg.966fbc5494af0133518ca4066ff084e4.jpg    Win_Reduce_2021-11-25_191305.jpg.e456fb35286842fed5d58b7c0a9a8147.jpg    VHD_WIMBOOT_2021-12-21_100603.jpg.87fd1e4d21b580139439bc73a4533b1d.jpg

Mini-10x64_2021-12-19_222319.thumb.jpg.7a5ede4ea129a6732014d456db9069cd.jpg    Mini-10x64_2021-12-20_094223.thumb.jpg.5144d44a678e3f63aa7203622fd182c8.jpg

Mini-11x64_2021-12-20_100053.thumb.jpg.c1aa71b2f7aecb1011f10ada2b164ba2.jpg    Mini-10x64_RAMDISK_2021-12-20_133321.thumb.jpg.c569d5c6273a2e435c9165127de8489c.jpg

Edited by wimb
Link to comment
Share on other sites

  • wimb featured this topic

всю инструкцию перечитал не чего не могу понять? если есть возможность как то объяснить то буду очень рад.

-------------------------------------------

I reread all the instructions, what can't I understand? if there is an opportunity to explain it somehow, I will be very glad.

Edited by ruslanishe
Link to comment
Share on other sites

  • 8 months later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...