663 replies to this topic

[samotc]

Thanks Internethandle, it's been fun, even though it took me 2-3 days, but it's nice to discover things for yourself, and learn along the way.

 

I am very stubborn, and when something resists me, I do not give up easily, otherwise I would not have been able to get into the adventure of Win PE Audio.

Although I have reduced the size of Win11PE a lot, I will keep insisting to reduce it more, instinct tells me that it is possible, I think it can be left in less than 400 mb with apps, drivers and everything else, also I would swear that the less size it has, best SQ, although they may be my impressions, and therefore a placebo effect, I don't know how to prove it, I will measure latencies to see if they corroborate this.

[internethandle]

Hi samotc,

 

Speaking of deletions, something I deleted (likely in services/drivers) has caused LatencyMon to not be able to launch so I have yet to measure latencies with it. Another thing on my list of things to try with PE. I share your stubbornness! Haha.

 

First on my list is Grub4DOS. I didn't have time this weekend, but may have some time next weekend. I think you may have answered this already, but is it possible to both launch Grub4DOS and have Grub4DOS locate a Win11PE ISO from the same USB drive? 

[samotc]

Hi samotc,

 

Speaking of deletions, something I deleted (likely in services/drivers) has caused LatencyMon to not be able to launch so I have yet to measure latencies with it. Another thing on my list of things to try with PE. I share your stubbornness! Haha.

 

First on my list is Grub4DOS. I didn't have time this weekend, but may have some time next weekend. I think you may have answered this already, but is it possible to both launch Grub4DOS and have Grub4DOS locate a Win11PE ISO from the same USB drive? 

 

YES !! 

 

all you have to do is format the USB drive as MBR, set it as primary and active partition and install g4D.

Then copy the files "grldr", "grldr.mbr", contents in the Grub4dos program folder, and the ISO file of Win11XPE Audio to the root of the USB and create a txt file and name it "menu.lst".

The content of the file can be this:

 

color blue/green yellow/red white/magenta white/magenta

timeout 30

default /default

 

title WINDOWS 11 XPE Audio ISO TO RAM

find --set-root --ignore-floppies /W11XPEAUDIO.iso

map --top --mem /W11XPEAUDIO.iso (0xff)

map --hook

chainloader (0xff)

 

title commandline

command line

 

title quit

quit

 

title reboot

reboot

 

title halt

halt

 

If you don't want to load the ISO into RAM, simply remove the --top --mem from the MAP line

 

If your PC is UEFI, don't forget to turn on CSM for legacy compatibility, on my wife's PC, which is UEFI, it works and boots perfectly.

[internethandle]

Thank you! Will give it a try this upcoming weekend.

[samotc]

SysWOW64 list rectification for foobar 2k:

 

If you want Windows audio drivers to run, add "AudioSes.dll" to the SysWOW64 folder, otherwise, even if you activate the services, the drivers will not load.

[internethandle]

Hi samotc,

I am having trouble understanding the steps to get Grub4DOS working, and Googling is proving to be not very helpful/confusing.

I have successfully formatted the USB drive to MBR with a primary and and active partition in a host Windows 10 OS using DISKPART in command line.

I have downloaded the latest version of Grub4DOS - 0.4.6a. I then copied the grldr and grldr.mbr files to the root directory of my USB drive as well as my Win11PE ISO and the menu.lst file I created based upon what you provided above.

When I reboot with CSM enabled, there is no option in my UEFI BIOS to boot from the drive.

I think I may be stuck on your step above where you say to “install g4D” - I can see from Googling that there is a GUI based program for Windows called “Grub4DOS Installer” - do I use that? I also see that yaya, the developer for G4D, has developed a UEFI compatible G4D at least in beta form as of late 2020, but as I understand it you would rather me use the “normal” G4D.

Sorry for the newbie questions, thanks for any help!

[samotc]

Hello internethandle! have no problem using it and install the G4D on the usb drive, you can also do it with Bootice:

Open the program and in "destination disk" select what corresponds to your usb pendrive, then click on "Process MBR" and a screen will be displayed with all the available types, select "GRUB4DOS 045c/046a" and finally click on "Install/Config "and you have it ready, then you just have to copy the files "grldr", "grldr.mbr" and "menu.lst" to the root of the usb and it should boot, check that you have disabled secure boot, G4D is incompatible.

 

 

Attached Files

•  Install_G4D_Bootice.jpg   119.97KB   3 downloads

[internethandle]

Thanks for the suggestion! Unfortunately, installing with Bootice in that way does not seem to solve the issue of the drive not appearing as bootable in the UEFI BIOS.

Have tried with two different USB drives now, same result, along with various combinations of settings around CSM in the BIOS menu - Secure Boot is indeed listed as disabled.

I am beginning to think this board (H170M-PLUS) has a faulty CSM module/function, as my experience with attempting to use CSM to get the Intel Optane drive to be seen was similar. It appears to be pretty set on only seeing GPT/UEFI drives as bootable, at least, no matter what I try. Have also flashed the BIOS to newest version with no results.

I will play around with some other things. Currently am trying to understand how to get Grub4DOS for UEFI to work. I seem to understand from posts on reboot.pro that it does not have full support for some menu.lst commands, however, so I am unsure how much that may serve me.

[samotc]

I'm sorry I can't help you more, because I don't know anything about G4D UEFI, personally I prefer BIOS, because it seems more versatile to me, Reboot.pro is a great forum, there are people there who can make many suggestions, and they are usually quite receptive to the requests for help, greetings.

[seeteeyou]

Ironically older BIOS releases from MSI seemed to be less flaky when it comes to the compatibility with Grub4DOS, though in this particular case below it's an AMD rather than Intel chipset

 

https://forums.tomsh...ing-it.3693742/

 

 

 

Other than that, not sure if this were relevant or otherwise?

 

https://rmprepusb.co...de-to-grub4dos/

I highly recommend that you download and use only this version of grub4dos 0.4.6a version 2020-02-29 (2019-09-09 or 2019-12-30 are also good) - Other versions of grub4dos, both older and newer, may be buggy!

 

 

 

Different version of the file grldr also seemed to make a difference for another scenario

 

http://jplay.eu/foru...-guide/?p=50938

 

And then here's the command to download another specific version of grldr

 

http://jplay.eu/foru...-guide/?p=53065

curl -N -r 1171456-1442666 -o grldr https://cdn.removed.us/ubcd/ubcd539.iso

SHA-1 hash value

10c262b395449b0555f18251aebcfa9c4aa12d64 *boot\grub\grldr

 

 

Sometimes USB 2.0 ports might actually provide better compatibility with bootable devices, even if those devices were designed to work with USB 3.0 ports in the first place.

 

BTW, it might be a good idea to start with tried-and-true stuff in order to figure out whether we're having hardware-related or software-related issues. Maybe we could try one of those USB 2.0 flash drives for starters and then go for something like 10PE19043x64(RamOS)_Admin_T.iso as follows

 

https://sites.google...te/toolsdnpe/pe

 

Write that ISO image to the USB 2.0 flash drive and then extract another file called seltool_T.7z to the root directory of that drive afterwards.

 

Both UEFI and Legacy BIOS are supported, therefore it should be fine in terms of testing purposes. If Grub4DOS were working with that USB 2.0 flash drive, then repeat the same steps with your Intel Optane M10 + USB enclosure afterwards.

 

Let's say Optane turned out to be OK as well, then we could take a closer look at those files and folders in order to find out what we actually need to get Grub4DOS working with a specific BIOS release for a motherboard.

[samotc]

Hi Internethandle, I just thought of another alternative, which sometimes works, is to format the usb leaving an EFI FAT32 partition and a primary NTFS partition.

You install G4D and copy its files to it (glrdr, grldr.mbr and menu.lst) and copy the ISO file to the NTFS partition.

It once worked for me on friends' PCs.

 

Good luck

[internethandle]

I stumbled upon the solution, thankfully!

Apparently my UEFI BIOS has a setting in its onboard USB port settings section that controls “USB Legacy” support. In my desire to disable all “unnecessary” functions in BIOS, I had disabled this too without thinking much about what it meant, but as it turns out the setting prevents any non-UEFI USB-attached drive from being populated in the boot section, regardless of whether CSM is enabled or not. Changing the setting back to “enabled” to allow for “legacy USB” support immediately allowed the USB-C to M.2 adapter to show up in the boot section, and Grub4DOS to load with a boot menu just as samotc said it would. I am glad, too, because “Grub4UEFI” was proving too complicated for me to understand.

Anyway, I can definitely see why it produces lower latencies just by how quickly it loads Win11PE into RAM. Lightning fast!

Thank you samotc!

I will comment on SQ after I get things settled in.

[samotc]

I stumbled upon the solution, thankfully!

Apparently my UEFI BIOS has a setting in its onboard USB port settings section that controls “USB Legacy” support. In my desire to disable all “unnecessary” functions in BIOS, I had disabled this too without thinking much about what it meant, but as it turns out the setting prevents any non-UEFI USB-attached drive from being populated in the boot section, regardless of whether CSM is enabled or not. Changing the setting back to “enabled” to allow for “legacy USB” support immediately allowed the USB-C to M.2 adapter to show up in the boot section, and Grub4DOS to load with a boot menu just as samotc said it would. I am glad, too, because “Grub4UEFI” was proving too complicated for me to understand.

Anyway, I can definitely see why it produces lower latencies just by how quickly it loads Win11PE into RAM. Lightning fast!

Thank you samotc!

I will comment on SQ after I get things settled in.

 

I'm glad !!

I am using LatencyMon Portable, which is much more comfortable, since I have reduced the size of Win11 PE to 440 MB and now I cannot install it, also having the portable is not worth it.

I have removed many drivers and components that I did not use, guided by the driver services that I had open, now I only have 42 left.

The test method is to put an audio track and run the test for 5 minutes, then check access to memory hard pages and see what processes use it, that's where the problem originates.

 

Curiously, the one that causes the most problems is the WIM file, Flatboot works better, but, without a doubt, the best of all is the G4D "ISO TO RAM" by far.

 

Hence my insistence that he try it.

 

Greetings.

[samotc]

I forgot to say that the Latencymon portable requires a lot of dlls to work, they are obtained with processhacker>>Properties>>Modules:

 

LatMon.exe, 0x400000, 5,68 MB, LatencyMon

advapi32.dll, 0x765c0000, 492 kB, Advanced Windows 32 Base API

bcrypt.dll, 0x74d40000, 100 kB, Windows Cryptographic Primitives Library (Wow64)

bcryptprimitives.dll, 0x778e0000, 400 kB, Windows Cryptographic Primitives Library

cfgmgr32.dll, 0x740c0000, 236 kB, Configuration Manager DLL

combase.dll, 0x75f20000, 2,54 MB, Microsoft COM for Windows

comctl32.dll, 0x75610000, 2,14 MB, Biblioteca de controles de la experiencia del usuario

comctl32.dll.mui, 0x2ae0000, 16 kB, Biblioteca de controles de la experiencia del usuario

comdlg32.dll, 0x770d0000, 764 kB, Common Dialogs DLL

credui.dll, 0x754f0000, 56 kB, Credential Manager User Interface

cversions.2.db, 0x3fc0000, 16 kB, 

cversions.2.db, 0x4030000, 16 kB, 

C_1252.NLS, 0x10000, 68 kB, 

C_1252.NLS, 0x1d0000, 68 kB, 

C_1252.NLS, 0xb20000, 68 kB, 

C_850.NLS, 0x9b0000, 68 kB, 

C_850.NLS, 0x9f0000, 68 kB, 

C_850.NLS, 0xb40000, 68 kB, 

dbgeng.dll, 0x74d60000, 5,73 MB, Windows Symbolic Debugger Engine

dbghelp.dll, 0x75320000, 1,78 MB, Windows Image Helper

DbgModel.dll, 0x74ca0000, 624 kB, Windows Debugger Data Model

dwmapi.dll, 0x73980000, 156 kB, Microsoft Desktop Window Manager API

fltLib.dll, 0x75500000, 36 kB, Filter Library

FWPUCLNT.DLL, 0x739e0000, 364 kB, API de modo usuario de FWP/IPsec

gdi32.dll, 0x77aa0000, 136 kB, GDI Client DLL

gdi32full.dll, 0x768c0000, 892 kB, GDI Client DLL

iconcache_16.db, 0x4540000, 1 MB, 

iconcache_idx.db, 0x4530000, 8 kB, 

iertutil.dll, 0x73ce0000, 2,18 MB, Utilidad en tiempo de ejecución para Internet Explorer

imagehlp.dll, 0x77350000, 104 kB, Windows NT Image Helper

imm32.dll, 0x77a70000, 148 kB, Multi-User Windows IMM32 API Client DLL

IPHLPAPI.DLL, 0x739b0000, 144 kB, IP Helper API

kernel.appcore.dll, 0x74b10000, 72 kB, AppModel API Host

kernel32.dll, 0x76380000, 960 kB, Windows NT BASE API Client DLL

kernel32.dll.mui, 0x2990000, 1,13 MB, Archivo DLL de cliente API BASE de Windows NT

KernelBase.dll, 0x76640000, 2,32 MB, Windows NT BASE API Client DLL

locale.nls, 0xa50000, 824 kB, 

logoncli.dll, 0x74c30000, 196 kB, Net Logon Client DLL

l_intl.nls, 0x1f0000, 12 kB, 

l_intl.nls, 0xa10000, 12 kB, 

l_intl.nls, 0xa40000, 12 kB, 

mpr.dll, 0x75900000, 100 kB, Multiple Provider Router DLL

msctf.dll, 0x76fa0000, 868 kB, MSCTF Server DLL

msvcp_win.dll, 0x75920000, 492 kB, Microsoft® C Runtime Library

msvcrt.dll, 0x777c0000, 776 kB, Windows NT CRT DLL

netapi32.dll, 0x755c0000, 76 kB, Net Win32 API DLL

netutils.dll, 0x74c20000, 44 kB, Net Win32 API Helpers DLL

normaliz.dll, 0x75e10000, 28 kB, Unicode Normalization DLL

ntdll.dll, 0x77ae0000, 1,66 MB, DLL del nivel de Windows NT

ntdll.dll, 0x7ffd2a040000, 2,03 MB, DLL del nivel de Windows NT

ole32.dll, 0x76470000, 1,3 MB, Microsoft OLE for Windows

oleaut32.dll, 0x76210000, 624 kB, OLEAUT32.DLL

profapi.dll, 0x74100000, 96 kB, User Profile Basic API

propsys.dll, 0x74120000, 836 kB, Microsoft Property System

propsys.dll.mui, 0x40e0000, 84 kB, Sistema de propiedades de Microsoft

psapi.dll, 0x777b0000, 24 kB, Process Status Helper

rpcrt4.dll, 0x75ce0000, 752 kB, Remote Procedure Call Runtime

rspDisMon32.dll, 0x75520000, 132 kB, 

rspSymSrv32.dll, 0x75550000, 404 kB, 

rspWmi32.dll, 0x755e0000, 124 kB, 

sechost.dll, 0x759a0000, 488 kB, Host for SCM/SDDL/LSA Lookup APIs

secur32.dll, 0x74bf0000, 40 kB, Security Support Provider Interface

SHCore.dll, 0x762b0000, 772 kB, SHCORE

shell32.dll, 0x769a0000, 5,99 MB, Windows Shell Common Dll

shlwapi.dll, 0x77890000, 296 kB, Shell Light-weight Utility Library

SortDefault.nls, 0x3610000, 3,23 MB, 

srvcli.dll, 0x74c00000, 116 kB, Server Service Client DLL

sspicli.dll, 0x74bc0000, 148 kB, Security Support Provider Interface

TextInputFramework.dll, 0x73a40000, 900 kB, "TextInputFramework.DYNLINK"

TextShaping.dll, 0x74a10000, 600 kB, 

 

Hope that helps.

[seeteeyou]

Just saw this interesting ISO image from Microsoft

 

https://software-dow...210604-1628.iso

https://oofhours.com...eployment-info/

There’s a new “Factory OS” available. What is this? Effectively, it’s the next generation of Windows PE built from the Windows Core Operating System (WCOS). It’s designed for OEMs to help with imaging, hardware testing, development, etc. But that doesn’t mean it can’t be used by others for “fun things.” This 7.5GB download will require some more investigation and experimentation. But a Windows PE environment with .NET Core, PowerShell Core, UWP support, and SSH is pretty cool.

 

https://twitter.com/...345760223580171

Factory OS is a bare-minimum version of Windows, designed for OEMs to test hardware and drivers without booting the full OS.

 

https://www.windowsc...windows-core-os

Windows Core OS strips Windows down to the bare minimum. It doesn't include any legacy components or features, and sticks to UWP as a core for the operating system as it's lighter and already universal.

 

Not sure if ASIO / WASAPI were even supported, though.

 

 

 

How can you launch a windows 10 app from command line?

https://superuser.co...nd-line/1522888

 

Quite a few UWP apps are available

 

https://www.microsof...wp/9nblggh4vvnh

https://www.microsof...es/9mwpjtxwtxlg

https://www.microsof...al/9p3jfr0clll6

https://www.microsof...er/9nblggh52s8c

https://www.microsof...-x/9pbhmtnp9037

https://www.microsof...rd/9nh6t2jdnrrr

https://www.microsof...al/9n797znkq5x6

https://www.microsof...rd/9mt04mwx772h

https://audirvana.co..._x64.appxbundle

https://audirvana.co...ease.appxbundle

 

Installers could be downloaded via this site

 

https://store.rg-adguard.net

[samotc]

Hello everyone, I have spent some time trying to reduce Win11PE Audio even more, in the end I have managed to reach 366 MB, with the usual applications and drivers installed, but it has been long and difficult, and I have had to do the task by way of reverse, not through Win10XPE, that's where I had reached the limit.

 

The starting point was the "boot.wim" file (index:1) of Windows 11 (22000.194), the "Insider Preview" versions on my machine > BSOD.

Then, taking as a reference the smaller version that I have made via WimBuiler (Win10XPE) I have been adjusting the files in the "WinSxS", "SysWoW64" and "System32" folders.

 

I've removed WinXShell, and all "Pecmd" references from system32, so it doesn't load, it starts with "starnet.cmd", so basically what's left is a Win11 PE "CORE", no GUI, I have left an "explorer++" support.

 

The most important problem has been "side-by-side configuration is incorrect", which has prevented me from installing drivers and applications, although I have managed to transplant them from the Win11XPE that I have, also doing offline registry imports, and it has worked, in case Otherwise it would have been impossible to achieve.

In the end there is a CORE with 366 MB, Bughead, Foobar2k, iFIAudioUSB ASIO drivers, DIYINHK_UsbAudio, and the essential ProcessHacker.

It is more inconvenient to handle, and I have not been able to download 11 processes, although in USB boot I can reach 38 active services (no network, no windows audio, no SATA).

After all this, what about the SQ?

It has improved, but it has not been as spectacular as the change from SERVER2019 CORE RAMDISK to WIN11XPE AUDIO, plus I have done some latency tests with Latencymon and they corroborate what was said (this also takes a long time to do).

I'm doing a little study on latency and SQ, with different Win11XPE configurations, (flatboot, wim, G4D-ISORAMDISK, boot from SATA/USB, BIOS optimized/not optimized, etc...) and there are differences in all of them, so far the best is ISO RAMDISK G4D from bootable USB (SATA disabled).

When I finish it, I promise to publish it, but it goes a long way, because just establishing a valid protocol seems quite complicated to me, and I don't find much reputable publication about it either.

What I do see is that SQ and latency are closely linked, and are inversely proportional

Greetings 

[internethandle]

Very interesting, samotc. I’d be interested in a guide if you provide one. I am used to working without GUI or with rather “inconvenient” OS implementations in the name of better SQ, so that would not bother me. I am not familiar with anything but the Win10XPE method of generating WinPE, so a guide would be appreciated whenever you find the time.

In the past, I have done much like you seem to be doing in deleting files from the Windows system directories, including system32 and SysWoW64, in other Windows OSes, but it is so slow going and frustrating that I don’t find I have the patience for it nowadays for attempting much with WinPE. I am glad you do have such patience! I do find that WinPE allows for much to be deleted after booting, but the utility of that is not clear to me. What little I have deleted in system32 in flatboot was, again, slow work, and I had a number of instances where it would not boot, so I settled for perhaps 30 to 50 files based on some of the batch files I found in a post on a Chinese forum seeteeyou had linked. I forget what they were now.

I have managed recently to get a number of running services/drivers to be forced into a “STOP_PENDING” state by deleting their sub-key entries in regedit after booting, and then issuing a sc stop command in command line. They are:

pdc
volume
wimfsf
wof
npfs
ntfs
partmgr
cng
msfs
mountmgr
disk
usbstor
ksecdd
fbwf

I am unsure what this accomplishes. Some services, when put into a stop pending state, seem to then not be accessible/able to be started, which would be advantageous in theory for overall footprint. On the other hand, the above method does not seem to unload anything from memory, at least when you view memory access in Process Hacker’s system information tab. Still, assuming this is doing something beneficial, the method leaves me with 27 “services” listed as “running” in Process Hacker’s services tab. Grub4DOS, as a happy side effect of using it to load into Ramdisk, also allows for those of us with UEFI BIOS to disable or delete the Windows UEFI driver, which normally always runs and is not stoppable after boot. Lastly, I have taken to stopping “condrv” right before closing everything but Opera GX and stopping DcomLaunch, as this creates some issues with some programs running (such as command line) but seems overall beneficial.

Speaking of which, Opera GX began to freeze and/or not launch properly after lsass.exe is terminated starting with version 84.0.4316.30 - the last version I found that works with lsass terminated is 83.0.4254.70 - this may also carry over for some version of Chrome for those that use that as a browser in PE, as Opera GX is based on Chromium, but I have not tested.

Because I have chosen to not use TIDAL app any longer and just use Opera GX to use TIDAL’s Web Player, I have deleted the entire SysWoW64 folder, as Opera GX does not need it to run, while the TIDAL app did. There is the disadvantage of not being able to use exclusive mode any longer with TIDAL, but also the advantage of the lack of memory and CPU usage that the app brought, as well as being able to delete the folder.

[seeteeyou]

Gaming-related software seemed to be beneficial since they're also all about latency reduction these days

 

https://www.realtek....d-i-awards-2021

https://www.station-...&id=646&lang=en

https://www.realtek..../rtl8125bg-s-cg

 

They're quite affordable as well

 

https://www.juplink....network-adapter

https://item.taobao....id=666222154930

 

 

 

Not sure if JCAT USB Card FEMTO were able to provide enough current for powering this?

 

https://www.juplink....network-adapter

https://item.taobao....id=644849645096

 

It would be interesting to find out if 2.5G NIC with the right gaming-related software were any good when compared to JCAT NET Card FEMTO, 16 CPU-direct PCIe lanes won't be shared by two slots if that NIC were connected to JCAT USB Card FEMTO

 

https://remont-aud.n...4/330-1-0-70656

https://remont-aud.n...06/34381538.png

 

Here's what we're getting from Intel

 

https://downloadmirr...Win10-11x64.exe

https://www.intel.co...ance-suite.html

https://www.intel.co...t-products.html

Priority 3 – Browsers and Streaming Video and Music

 

The priority of each application could be changed manually

 

https://www.msi.com/...shot-advantages

 

 

 

Most likely there's nothing special about the hardware whatsoever, therefore it's kinda hilarious that pretty much anything with Realtek RTL8156B could also get that Killer E3100U driver installed once we've disabled driver signature enforcement

 

https://post.smzdm.com/p/a850493n/

 

Windows 10 was mentioned in that guide linked above, it should be pretty much the same deal with Windows 11

C:\Program Files\Killer Networking\Killer Control Center\Production\Windows11-x64\E3X00\e3k25cx21x64.inf

C:\Program Files\Killer Networking\Killer Control Center\KillerNetworkExtension.inf

Here's the same Windows 11 driver from Microsoft

 

http://download.wind...836c804d2fa.cab

https://www.catalog....bc-87df05182a62

 

 

 

Replace Killer wifi driver on xps 7590 with Intel AX200 driver???

https://www.reddit.c...590_with_intel/

 

Even drivers for Intel Wi-Fi cards were interchangeable, it just really doesn't make sense to pay more for anything with their own Killer brand at all after the acquisition of Rivet Networks

 

https://zhuanlan.zhihu.com/p/357778714

https://blog.csdn.ne...tails/123196021

[Marcin_gps]

 

They're quite affordable as well

 

https://www.juplink....network-adapter

https://item.taobao....id=666222154930

 

 

 

Not sure if JCAT USB Card FEMTO were able to provide enough current for powering this?

 

https://www.juplink....network-adapter

https://item.taobao....id=644849645096

 

 

The specs mention External Power Supply  and 12V, so USB Card will now power it

 

Regards, 

Marcin

[samotc]

Hi Internethandle, making a guide like the pdf would take me at least 3-4 weeks full time, I'll give you a few detailed instructions, I think they will be enough for you. If you don't need SysWOW64 it will be much easier, as it was the source of my biggest ("side by side") problems caused by Visual C+ mismatches, and I couldn't solve it, just dodge, although it was enough for my purpose.

 

1. Download from Microsoft ("Windows-ISO-Downloader.exe"):

 

a - Windows Server insider Preview_xxxxx.iso

b - Windows_InsiderPreview_ADK_en-us_xxxxx.iso

c - Windows_Preinstallation_Environment_en-us_xxxxx.iso

 

being xxxxx the same in all.

 

2. Install b and c (in host)

 

3. Create WinPE:

 

It will give you several options: x86, amd64, ARM64, ARM86. Choose the one that suits you.

 

4. Created WinPE.wim:

 

Flatboot on VHD / USB (to your liking)>>> Boot (On my PC always BSOD, that's why I opted for the "path boot.wim index:1" of the Windows 11 iso es-ES 22000.194) but maybe it's because my machine is a bit old (no uefi, no tpm, no secure boot).

 

5. Boot Flatboot and check that it loads

 

6. Install drivers and apps as you did for "via Win10XPE"

 

a - Positive result >>> goes to the reduction stage (8)

 

b- Negative result >>> driver transplant (7), try portable apps, app transplant (7)

 

7. Transplant of Drivers-Apps:

 

Taking as reference a Win11PE Audio that you have already made and working, and checking the versions of the dlls:

 

a - Copy the installed drivers folders (in Win11PE) from "Program Files" to "Program Files"

 

b - Copy the .inf from "\Windows\INF" to "\Windows\INF"

 

c - Copy the .sys from "\Windows\System32\drivers" to "\Windows\System32\drivers"

 

d - Copy the .dll from "\Windows\System32\" to "\Windows\System32\"

 

e - Copy "Folder APP" from "\Users\Default\AppData\Roaming\" to "\Users\Default\AppData\Roaming\"

 

f - Import (OFFLINE) the "regfile.reg" you created when making Win11PE via the "Win10XPE" program.

 

g - Check that they work (if not, check what dlls it asks for, look for them in the Win11XPE Audio reference and copy them to the new one in the same location)

 

8. Reduction:

 

a - WinSxS >>>

 

With the program "WinSxS_Reduce_Trusted" which can be downloaded from here:

 

 http://reboot.pro/to...e-3#entry215317

 

b - SysWow64 >>>

 

If you don't need it, remove it (saves 58 MB); Otherwise, it creates a list of files from each SysWOW64 and leaves the new one with    the  same ones as the one from Win11XPE.

 

c - System32 >>>

 

Same as above. If you are going to remove SysWow64 you can delete wow64.dll, wow64base.dll, wow64con.dll, wow64cpu.dll, wow64win.dll and wowreg32.exe.

 

The minimum size I've been able to achieve, without SysWow64, without f2k, just with InfinityBlade + Drivers + RewriteData + ProcessHacker, is 286 MB fully functional, and I think more can be removed. In a way I have made myself an "INFINITYBLADE_PE"

 

I think this will be enough for you to do it, it is an interesting way to create "PE_AUDIO applications" that do not need to be installed in an OS, since they have it "incorporated", and of course, it is what sounds best. "InfinityBladePE" sounds much better than InfinityBlade within Win11PE AUDIO, and the latency tests with LatencyMon confirm it, as well as my ears, hahaha..

 

The same can be said for F2K_PE, both on x86 and x64.

 

Greetings