714 replies to this topic

[seeteeyou]

Dependencies could be so much fun, in some cases it's truly necessary to keep certain (genuine) processes running in order to satisfy the prerequisite(s) of a specific application.

 

OTOH, sometimes we might be able to get away with dummy processes (i.e. it's merely checking the presence without actually depending on those processes at all) that could do nothing more than "pretending" to be lsass.exe etc.

 

Basically we could create a dummy batch script and then convert that into an executable as mentioned below

 

https://superuser.com/a/1003758

https://github.com/tokyoneon/B2E

https://www.portable...re.com/?id=1660

https://www.battoexe...xeconverter.exe

https://web.archive....e_Converter.zip

https://sourceforge.....0/BatToExe.exe

https://www.softpedi....shtml#download

 

Or simply grab something here and then rename that to whatever we want

 

https://github.com/m...er/nop/releases

 

 

 

I still dunno why it's sounding harsh (without the presence of "genuine" lsass.exe) since we're already going the extra miles to strip everything WAY down, though eventually we might consider emulating what Emile and Nenon were doing by upgrading to Asus WS C621E SAGE with dual Xeon Silver 4114 / 4210 while turning that into a headless setup without KVM (keyboard / video / mouse) etc.

 

https://www.reddit.c...ss_without_gpu/

https://www.reddit.c..._on_a_headless/

 

Since we're already having network connections of the sake of TIDAL, I guess that running stuff like TightVNC might still produce less noise when compared to the "harm" that's potentially caused by GPU + monitor in addition to PS/2 keyboard + mouse

 

https://sourceforge....files/TightVNC/

[samotc]

Hi, Internethandle, effectively, suspending "winlogon.exe" then I can kill "pecmd.exe" and the last instance of WinXShell, leaving 12 active processes (except ProcessHacker)

Regarding the user, it is still NTAUTORITY / SYSTEM, what happens is that after killing "lssas.exe" for whatever reason, you restart ProcessHacker, it no longer takes the user, on the other hand, if you don't restart it after killing ProcessHacker, it keeps it , see it in the screenshot that I attach.

Greetings.

 

 

Attached Files

•  12_processes.jpg   110.65KB   5 downloads

[samotc]

And thank you very much for your suggestions.

[internethandle]

Hi samotc,

Great! Thanks for confirming that worked, I am very happy it did. It will be interesting to hear your reports on sound quality given the lowest I can get is 14 processes with my need for Windows mixer (AudioSrv and AudioEndpointBuilder).

That makes sense about restarting Process Hacker - I had not considered that might happen. Helps to confirm that lsass is just breaking something about Process Hacker’s user name display and not that anything is changing about WinPE’s permissions.

Happy new year.

[samotc]

Good evening, I have made a sound comparison between Win11XPE Audio with explorer interface (14 active processes) and Win11 XPE WinXShell interface (12 active processes)

 

Listening equipment:

 

Speakers: Xeed Supreme with artisan CAT 7 braided cables

 

Amplifier:

 

SE Triode 320B XLS 12 W per channel

SS Nelson Pass F5 + BA3 Preamp 20 W per channel

 

DAC: DIYAUDIO OMERIQUE (2x Burr Brown PCM 1704k per channel, discrete output)

                  IFI iDSD nano

 

Wiring: DAC AMP: 2x Cardas Clear 0.5 m

 

Source:

 

Streacom FC9 Alpha Fanless

PPA PicoPSU linear source and HDPLEX 200 w

Intel DH67BL motherboard

Intel i5 2.67 Ghz processor

RAM 32 GB (4x8GB DIMM Kingston)

PPA v4 OCXO USB Card

IFI iGalvanic 3.0

IFI micro iUSB

USB PC Cabling - Wireworld Platinum Starlight 7 USB 2.0 A-B DAC

HDPLEX directly powers SSD OS and PPA v4 OCXO

 

Listening tracks:

 

01. Marc-Antoine Charpentier (Les Arts Florissants Dir. William Christie) - Te Deum [SACD DSF] tracks 1-6

02. Tchaikovsky 1812 - Erich Kunzel Cincinnati Pops Orchestra (SACD DSF) track 1

03. Arne Domnerus Group -  Jazz at the Pawnshop 30th Anniversary (2006) [3 SACD] CD1 track1

04. Bizet. Chabrier - Jean Morel, Royal Opera House Orchestra - 1959, 2017, [APC 2327 HR  DSD256] track 01. España Rapsodie.dsf

05. Paco de Lucia, Al Di Meola, John McLaughlin (Compilation Friday_Passion) - Friday Night In San Francisco (IMPEX IMP6029 LP Vinyl Rip DSD 256) track 1

06. Pat Metheny Group - Travels (ECM Records PROZ-1113/4 SACD DSF) track 1

07. Miles Davis - Kind of Blue (MFSL 2015 SACD DSF) track 1

08. Rameau - Le Concert des Nations dir. Jordi Savall - L'Orchestre de Louis XV (SACD DSF) tracks 1-5

09. Vangelis - Blade Runner [Audio Fidelity AFZLP154] (DL103 LP DSD128 Vinyl Rip) tracks 4,5,7.

10. Al Stewart - Year Of The Cat [MFSL MFCD 803] tracks 2,9

11. Amarcord - Nino Rota (CSE 003) - track 1

12. Elton John - The very best of Elton John CD2 track 4

13. Eagles - Hell Freezes Over (K2HD) {2011} [GEFFEN 5331147] track 6

14. Loreena McKennitt - Nights From The Alhambra (QRDVD2-PBS-P DVDA 24-48 Rip) tracks 1, 4

15. Mark Isham - Mark Isham (Virgin America CDVUS 261 112) track 9

16. Nancy Sinatra & Lee Hazlewood - The Hits Of Nancy & Lee (Reprise Records RS 6273 LP 24-192 Vinyl Rip) track 4

17. The Cranberries - To The Faithful Departed (LP 24-192 Vinyl Rip) track 3

18. Wim Mertens - Maximizing The Audience track 3

19. Wim Mertens - Personal Collection track 13

 

I can only say that after a detailed listening, both are light-years away from Server 2019 Core in RAMDISK, with 12 active processes (WinXShell) the difference is even greater, the degree of transparency, crystal clarity, precision of the sound scene, Timbral and micro-detail is incredible, the sound is very smooth analog, without grain, the silky highs, the very real voices nothing nasal, the precise and articulate bass.

I have rediscovered all my recordings, it is as if I have never heard them before, for the large amount of new information appreciated.

I don't think I will use another OS again.

 

[keith_correa]

Good evening, I have made a sound comparison between Win11XPE Audio with explorer interface (14 active processes) and Win11 XPE WinXShell interface (12 active processes)

<snip>


I can only say that after a detailed listening, both are light-years away from Server 2019 Core in RAMDISK, with 12 active processes (WinXShell) the difference is even greater, the degree of transparency, crystal clarity, precision of the sound scene, Timbral and micro-detail is incredible, the sound is very smooth analog, without grain, the silky highs, the very real voices nothing nasal, the precise and articulate bass.
I have rediscovered all my recordings, it is as if I have never heard them before, for the large amount of new information appreciated.
I don't think I will use another OS again.

Hi! I thought you found Win 11 cold and analytical when compared to Win 10. What made you change your mind?

[samotc]

Hi, Keith, what has made me change my mind is the time, that is, the more I listened to Win11XPE the more I liked it, throughout the days after listening to Win11XPE, when I return to Wn10XPE I notice that I like it less, it seems to me more fuzzy, less clean.

I won't tell you anything if I go back to Server Core RAMDISK, I find it unbearable.

I think I need some time to assimilate the changes.

[samotc]

Anyway we are talking about small but significant differences between Win10-11 XPE, less audible on the SS Nelson Pass F5 than on the SE 320XLS triode, here they are clearer.

Of course, regarding the Server Core 2019 RAMDISK, they are very significant, in fact I have removed it from my PC.

[internethandle]

Have been working with Win10PE so am attempting a Win11PE now based on your report.

Unfortunately, it appears there might be some issue with integrating the native USB Audio 2.0 Windows driver that my DAC needs to function and Win11PE. The same integration procedure I successfully employed with Win10XPE for Win10PE does not lead to Win11PE installing the driver correctly. Instead, while it successfully associates the driver with the DAC, Device manager claims the driver isn’t digitally signed. Turning test signing on was no help, although that would seem odd given it is a Microsoft provided driver. Have also tried multiple versions from different Windows installs other than just the one in the source Windows 11 ISO, no dice. Works fine in “normal” Windows 11 from the same source ISO installed on another drive. Frustrating!

A word to those going this route: you will need the newest version of Win10XPE for Windows 11 to be supported - I first attempted with an older version and while Win10XPE would go through with making an ISO, it would not boot properly. Also, if, like me, you have an older chip (Skylake in my case) and want to install Windows 11 normally (not PE), be sure to use Rufus to burn to USB and select “Non-TPM/secure boot”, otherwise you will not be able to complete installation due to Microsoft claiming your hardware is incompatible.

[seeteeyou]

https://www.schiit.com/drivers

For Windows 10: No drivers necessary.

 

https://www.schiit.c...cing-unison-usb

Unison USB is Schiit's unique, proprietary USB input that is the result of 2 person-years of development. Running on a general-purpose Microchip microprocessor (rather than a typical XMOS or C-Media solution), Unison USB provides superior UAC2 performance at very low current draw from the host, as well as complete electromagnetic and electrostatic isolation.

 

https://audiophilest...comment-1121607

This past week I bought a new DAC on the used market (Schiit Yggdrasil A2 with Unison USB), and it worked fine for a few days.

 

https://www.head-fi....4#post-15166201

One question for Jason & co.: since Unison USB now is taking advantage of Windows 10's post-2017 UAC2 adoption, I take it that there won't be any "native" ASIO functionality in Windows sans maybe ASIO4ALL, right? No big deal if not, I'll likely just run WASAPI.

 

https://www.head-fi....4#post-15166792

For ASIO, we use ASIO2WASAPI for testing. The APx reports were done with ASIO2WASAPI. For listening, we plug and chug, no need for crazy interface stuff.

 

 

 

Mounting the BCD Store as a Registry Hive
http://www.mistyproj...gistry_hive.htm

Generic Elements
http://www.mistyproj...des.htm#generic

Disabling BCD testsigning option using registry
https://stackoverflo...-using-registry

How to check driver code signing policy is enabled and actually work?
https://stackoverflo...d-actually-work

HKLM\BCD00000000\GUIDXXX\Elements\12000030
HKLM\BCD00000000\GUIDXXX\Elements\16000048
HKLM\BCD00000000\GUIDXXX\Elements\16000049

Boot Configuration Data settings and BitLocker
https://docs.microso...s-and-bitlocker

0x12000030	all	loadoptions
0x16000048	all	nointegritychecks
0x16000049	all	testsigning

Most likely that should do the trick.

[samotc]

Hi, Internethandle !

 

Sorry for your problems with the USB audio 2 driver installation.

I suppose you have tried this, with the command line:

 

bcdedit.exe / set nointegritychecks off

 

bcdedit.exe -set loadoptions DISABLE_INTEGRITY_CHECKS

 

bcdedit.exe -set TESTSIGNING ON

 

Of course, first executing Registry changesview> Snapshot1 >> type commands >> Snapshot2 >> OK >> Export regfile >> Import regfile offline with Remote Registry or another.

 

Another alternative is to type F8 at startup to disable the signature drivers.

 

The thing that Win11XPE sounds better than Win10XPE, is MY opinion, and with MY computer and MY system, which may not match yours, the difference is small, but clearly audible, in the case of CORE SERVER 2019 RAMDISK it is VERY BIG, it gives sorry to hear it after Win11 (or 10) XPE.

That's why I always say that you have to try everything first.

Regards, hope you can solve the problem

 

Does the DAC have no specific drivers?

I have a Khadas DAC that also uses Windows USB2 but I can additionally download a specific driver from its website, which would be installed via Registrychangesview in the flatboot.

[internethandle]

Thanks for all the thoughts, seeteeyou and samotc.

Yes, have tried testsigning/nointegritychecks settings, to no avail. Doesn’t make much sense they would work, anyway, since this is a Microsoft driver/service, but I did look.

I’ll be looking today to see if I can spot any relevant differences in comparing Win10PE’s registry and Win11PE’s for the same device. I’ve been able to inject values that way before, similar to samotc’s RegistryChangesView method I suppose, when I had a new USB receiver board in an old DAC and a heavily stripped Windows 10 that did not want to install its drivers. I was only able to get WASAPI working at the time with that method, but worth a shot.

ASIO4WASAPI is maybe an option, but may be difficult to shoehorn into TIDAL app/web browsing. Likely would work for file playback if at all.

Yes unfortunately only USBAudio2.sys is a working driver for the Schiit Yggdrasil DAC I have.

I do suspect I may not be able to overcome this without a lot of research and time, if at all. It makes some sense to me that, given how relatively new Windows 11 is, there could be some native driver instability in certain environments, such as PE, that Microsoft has just yet to become aware of and implement a fix for. I have to figure I am one of the first to be trying to inject this particular native driver into a Windows 11 PE environment since it is not a typical use case. Even with W10PE, while the injection works, there are some peculiarities such as differences in how the DAC displays in device manager vs. “normal” W10.

[seeteeyou]

Maybe keep trying the latest builds whenever their Insider Preview releases are updated, they could be downloaded with that New Additions option of Windows-ISO-Downloader.exe

 

https://www.heidoc.n...-Downloader.exe

https://www.heidoc.n...o-download-tool

 

Besides, you could take a look at the ISO images of Windows 11 PE build 22523 as well

 

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

5.無法安裝驅動

 

(FYI - that means they already fixed the problem with "unable to install driver" at some point.)

 

Traditional Chinese and Simplified Chinese versions (good enough for verifying registry keys etc.)

 

11PE22624x64(RamOS)_Admin_T.iso

 

11PE22624x64(RamOS)_Admin_C.iso

 

 

 

I guess that maybe we could also report that to Chris just in case there might be something else that could be done on his end?

 

https://github.com/C...Win10XPE/issues

 

Other than that, sometimes 22000.194 might be a better bet than other builds as well

 

https://github.com/C...10XPE/issues/14

Anyway, the build processed successfully using 22000.318 but upon booting up my Win10XPE flash drive I received the error "Sign-in process initialization failure. Interactive sign-in process initialization has failed."

 

I then went back to rebuild my project and noticed that I used 22000.318 so I downloaded from TechBench 22000.194 and all worked fine again.

 

22000.194

https://techbench.lu...ad.html?id=2069

 

Win11_English_x64.iso (brought to you by software-download.microsoft.com)

 

Evaluation

https://software-dow...64FRE_en-us.iso

 

 

 

22000.318

https://techbench.lu...ad.html?id=2093

 

Win11_English_x64v1.iso (brought to you by software-download.microsoft.com)

 

Evaluation

https://software-dow...64FRE_en-us.iso

 

 

 

UUP Media Creator

https://github.com/g...reator/releases

 

Latest 22000 builds

 

https://uupdump.net/known.php?q=22000

 

 

 

(Note from Captain Obvious - it doesn't support any Insider Preview releases / homebrew ISO images.)

 

Windows and Office Genuine ISO Verifier

https://genuine-iso-...fier.weebly.com

https://genuine-iso-...so_verifier.rar

 

 

 

Finally here's yet another (potential) issue that might affect anything later than version 20H1

 

https://www.tenforum...tml#post2109995

After efforts to try to support 20H2. There is no need to go further

The result is not really reliable, depending on the components or applications used...

 

In Windows 10 version 2009 - 20H2 ISOs, update packages were not added to winre.wim, as it is normally done!

And so, the Versions between winre.wim and Install.wim do not match that is a source of incompatibilities and problems.

In addition to the C:\ drive in the registry instead of X:\ (already fixed)

TechBench ISOs and Media Creation Tool ISOs are concerned, ISOs created via UUP files look good.

 

Except for UUP ISOs, It is preferable to use Windows 10 version 2004 - 20H1 and forget Windows 10 version 2009 - 20H2

 

In case the versions do not match, I have added a message to inform and ask to continue construction or not (No by default).

Winre.wim Version (10.0.19041.1) Does Not match Install.wim Version (10.0.19041.631)

 

Incompatibilities Are Likely to Occur With Perhaps an Unreliable Result.

 

Preferably Use Windows 10 version 2004 - 20H1

 

Continue Anyway ?

 

In other words, are UUP ISOs supposed to be our best friends or something?

[samotc]

Hi, Internethandle

 

Does your DAC work on a "normal" Windows 11 installation?

If so, you could copy all the files related to the USBAudio2.sys driver from the Windows 11 "Normal" installation to Windows 11 XPE, and export the registry values from the "normal" Win to the win XPE, keeping in mind that Any reference to "C:\ xxxx" must be replaced by "X:\".

If not, I don't know how to help you.

 

As Windows 8.1 does not have a USBAudio2.sys driver, does its DAC have a specific driver for Windows 8.1? , it may work if you install it.

 

Greetings and luck.

[seeteeyou]

I'm assuming that \Drivers\DrvInstPatch Plugin might be somewhat helpful, not sure if that were still good for Windows 11 PE?

 

http://win10se.cwcod...nstPatch.Script

 

And then there's also this registry key that could be used to fool the installation of driver, just change 1 back to 0 after we're done

REG Add HKLM\SYSTEM\Setup /f /v SystemSetupInProgress /t REG_DWORD /d 1

Finally maybe we could grab a copy of (already patched) DrvInst.exe from either ISO image and use that to get the driver installed instead

 

11PE22523x64(RamOS)_Admin_T.iso

 

11PE22523x64(RamOS)_Admin_C.iso

 

 

 

FYI - here are some alternatives for getting started with PE and the first one could be installed from this reflect_setup_free_x64.exe file
 
http://updates.macri...ch=1&redirect=Y
 
Macrium Reflect 8 Free
https://www.macrium.com/reflectfree
https://www.macrium....free-is-out-now

PE 11. Rescue media can now be built on WinPE 11. This uses the Win11 kernel and includes updated inbox drivers for better hardware support.

 
The Macrium Rescue Environment
https://blog.macrium...nt-cca57a4ebc61
https://knowledgebas...cue Environment
https://knowledgebas...e Media Builder
https://knowledgebas...ng rescue media
https://knowledgebas...eflect recovery
https://knowledgebas...ication support
https://knowledgebas...PE Rescue Media
https://knowledgebas...s boot problems
https://knowledgebas...ardware drivers
https://knowledgebas...t to Windows PE
https://knowledgebas...t to Windows PE
https://knowledgebas...he Rescue Media
 
Or start reading page 282 of this PDF file
 
https://updates.macr...de.pdf#page=282
 
If we're only interested in downloading those necessary components for building an image of PE, click the Options button under the Download Location and Options section after running this file below
 
http://updates.macri...flectDLFull.exe

 
A comparison among different options here
 
https://knowledgebas...Macrium Reflect
 
Basically we could figure out what it's actually doing in the background by checking this features.xml files as follows
 
http://updates.macri...featurelist.asp
 
(Take a look at anything related to pe11x64 etc.)
 
PowerShell
 
https://github.com/p...er/10.1.22000.1
https://github.com/p...WinPEAddons.ps1
 
A list of files to be downloaded manually
 
https://sharetext.me/raw/bpiuuiz03w
 
20348 = Windows Server 2022
 
https://sharetext.me/raw/hactzeutwt
 
Extract those *.MSI files manually
 
https://lessmsi.activescott.com
 
 
I just wanna highlight that both pe11x86 and pe11x64 are available, while that GUI as shown above actually gave us both 32-bit and 64-bit options
 

<component id="pe11x86">
<name>WADK x86 Components</name>
<description>Components for WADK x86 rescue media</description>
<savepath/>
<savefilename>pe11x86.zip</savefilename>
<file>pe11x86wim</file>
<file>pe11x86files</file>
<file>pe11x86tools</file>
<file>pe11x64tools</file>
<file>pe3x86tools</file>
<file>pe3x64tools</file>
</component>

32-bit version of Windows wouldn't have anything to do with driver signature enforcement whatsoever, that means we could simply grab that USBAudio2.sys etc. from 32-bit version of Windows 10 Version 21H2
 
https://techbench.lu...ad.html?id=2084
 
Win10_21H2_English_x32.iso (brought to you by software-download.microsoft.com)

 

https://docs.microso...igning-a-driver

All drivers running on 64-bit versions of Windows must be signed before Windows will load them. However, driver signing is not required on 32-bit versions of Windows.

 

MajiorityClean and LemonadeElitest etc. won't work, though.

 

 
 

As Windows 8.1 does not have a USBAudio2.sys driver, does its DAC have a specific driver for Windows 8.1? , it may work if you install it.

 
Schiit Yggdrasil DAC came with the same Unison USB interface and Schiit Audio never had anything for Windows 8.1 at all
 
https://www.head-fi..../#post-16136415
 
Only providing drivers for their older Gen 2 and Gen 5 etc.
 
https://www.schiit.com/drivers

[Xp18]

I added VHD boot to system BCD and check that it boots and works.
I installed the drivers for Win10 XPE but something went wrong with my DAC driver. My dac uses usb combo driver 384 Amanero.
Can anyone support for me?

[seeteeyou]

My dac uses usb combo driver 384 Amanero.

 

It's a bit tricky to get Windows Installer working under Windows PE, only partial support could be found with this one called Samare

 

https://github.com/E...Samare/releases

http://bbs.c3.wuyou....read&tid=425831

http://bbs.c3.wuyou....read&tid=426094

 

Therefore it's easier to try this InjectDriversPE.7z instead

 

https://www.tenforum...tml#post2355644

 

Let's get a copy of lessmsi as well

 

https://lessmsi.activescott.com

 

Download SetupASIO64.msi and then use lessmsi to extract 2 files as shown below

 

https://amanero.com/...SetupASIO64.msi

c3asio.dll

c3asio64.dll

 

Download w10.zip and then unzip 9 files afterwards

 

https://amanero.com/...ges/w10/w10.zip

cmb384.inf

cmb384.sys

cmb38464.sys

dpinst.xml

eula.txt

hifntamd64.cat

hifntx86.cat

Setup32.exe

Setup64.exe

 

Please make sure that we're putting all 2 + 9 = 11 files inside the same folder.

 

 

 

Finally extract InjectDriversPE.exe from InjectDriversPE.7z and we'll run InjectDriversPE.exe accordingly, then we'll be prompted to find boot.wim of Windows PE

 

Select the boot.wim file to permanently inject drivers into

 

Simply go to that folder with all 2 + 9 = 11 files as mentioned above

 

Select the folder containing the drivers (Subfolders w/spaces Allowed)

 

Update the ISO image of Windows PE with that new boot.wim (e.g. with UltraISO) and let's see how it goes.

[samotc]

Hola, Xp18.

Another alternative to seeteeyou's answer, is to redo the XPE from the beginning, and in the "Main Interface" screen add support for Windows Installer by checking the corresponding box, as I show in the screenshot that I attach

Attached Files

•  windows installer.jpg   115.37KB   5 downloads

[samotc]

Compiling on the optimization of WinXPE Audio (10 or 11) I am going to detail here some processes that perhaps in the guide are passed succinctly, since the main purpose was not that.

Here I have compiled ideas put forward by Internethandle and seeteeyou, whom I thank for their valuable contributions.

 

DISABLE THE NETWORK IN WIN XPE AUDIO:

 

I only recommend doing it if we are sure that we will not need it at any time for the reproduction of music files.

or for the operation of the player, if so, proceed:

 

1. CREATION OF FILE "Unattend.xml" IN WINDOWS \ SYSTEM32 IN FLATBOOT VHD OR USB:

 

Open Notepad and paste the following text:

 

<?xml version="1.0" encoding="utf-8"?>

<unattend xmlns="urn:schemas-microsoft-com:unattend">

    <settings pass="windowsPE">

        <component name="Microsoft-Windows-Setup" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" processorArchitecture="AMD64">

            <EnableNetwork>false</EnableNetwork>

        </component>

    </settings>

    <cpi:offlineImage cpi:source="" xmlns:cpi="urn:schemas-microsoft-com:cpi" />

</unattend>

 

Done this, save the file as "Unattend.xml".

 

2. MODIFICATION OF THE FILE "winpeshl.ini" OF WINDOWS \ SYSTEM32 IN FLATBOOT VHD OR USB:

 

Make it call "unattend.xml"

To do this we edit the file "winpeshl.ini" with notepad leaving it like this:

 

[LaunchApps]

wpeinit /unattend="%SystemRoot%\system32\Unattend.xml "

 

3. MODIFICATION OF "pecmd.ini" IN WINDOWS \ SYSTEM32 IN FLATBOOT VHD OR USB:

 

Edit "pecmd.ini" with notepad and go to the SUB Netinit section and leave it like this:

 

_SUB NetInit

 

//=Load Network drivers at startup

//=EXEC =@!%WinDir%\System32\Drvload.exe %WinDir%\inf\athw8x.inf %WinDir%\inf\netathr10x.inf %WinDir%\inf\netathrx.inf %WinDir%\inf\netbc63a.inf %WinDir%\inf\netbc64.inf %WinDir%\inf\netrtwlane.inf %WinDir%\inf\netrtwlane_13.inf %WinDir%\inf\netrtwlanu.inf %WinDir%\inf\netwbw02.inf %WinDir%\inf\netwew00.inf %WinDir%\inf\netwew01.inf %WinDir%\inf\netwlan92de.inf %WinDir%\inf\netwlv64.inf %WinDir%\inf\netwns64.inf %WinDir%\inf\netwsw00.inf %WinDir%\inf\netwtw02.inf %WinDir%\inf\netwtw04.inf %WinDir%\inf\netwtw06.inf

 

//=EXEC !=SetWG.exe WORKGROUP

 

//=EXEC @!%WinDir%\System32\Net.exe Start Wlansvc

//=EXEC @!%WinDir%\System32\Net.exe Start WinHttpAutoProxySvc

 

//=Launch PENetwork

//=EXEC X:\Program Files\PENetwork_x64\PENetwork.exe

 

//=Remote Desktop Server Connect (Uncommented By RDC Plugin)

//=EXEC @!%WinDir%\System32\mstsc.exe /v:

 

_END

 

Then save the changes and close the file.

Now we have the network disabled and we can deactivate more processes and services.

 

After disabling the network we will continue with the disabling of services.

To do this, we will start the PC with WinPE Strelec, mount the VHD or insert the USB Pen that contains the Win11XPE Flatboot.

Once this is done, we will go to Programs >>> Utilities >>> Remote Registry and open it, we will navigate through the drive letter that contains the Flatboot (VHD or USB)

to \ Windows and the registry window will open.

 

Navigate to [HKEY_LOCAL_MACHINE \ System \ ControlSet001 \ Services \

 

Go deactivating services (change "DWORD value" to 4 in hexadecimal) until leaving these 4 active (seen with "services.msc")

 

LSM (local session manager)

RpcEptMapper (RPC endpoint mapper)

DcomLaunch (DCOM Server Process Launcher)

RPC (remote procedure call)

 

The arrest of any of them causes the collapse of the system, we are at the limit.

 

GRADES.-

 

If we have made the XPE with the Explorer interface, WE WILL NOT BE ABLE TO DISABLE the "CoreMessaging" service, so we would have 5 active services left.

On the other hand, if we have the WinXShell interface, YES we can disable the "CoreMessaging" service, leaving 4 active services.

I do not take into account the services dependent on devices and drivers that ProcessHacker shows, because each PC is a world and I do not dare to recommend deactivating any driver or device, outside of mine, because I do not know the use that each one makes of theirs.

If the Windows audio mixer is needed for some reason, we will not be able to disable the "Audiosrv" and "AudioEndpointBuilder" services either.

 

After leaving these services active, on my PC there are only 18 active processes in the background, excluding ProcessHacker.

 

If we want to refine even more, we have margin, we can only reach 12 processes !! (with WinXShell) or 13 with Explorer.

 

This will go into the Extreme Optimization part.

 

[samotc]

WINDOWS 11 XPE EXTREME OPTIMIZATION:

 

The goal is to get 12 processes in the background, since we only have 4 active services, with this the sound is impressive, far superior to XPE with standard refinement, and light-years away from Windows Server 2019 Core in RAM.

I have done the tests with both Foobar and Infinity Blade; Win11XPE with Foobar is far superior to CORE 2019 RAMDISK with Infinity Blade and WTFPlay 0.75, which was the best version so far, and refined to these extremes much more.

We will do the refining process in 2 phases, the first one is not dependent on the process deactivation sequence, so you could create a script for it, but the second one is, and there must also be time between one and the other. deactivation, so I don't know if a script could work.

Before deactivating anything, the audio player that we are going to use must be launched, as well as the driver panel, to verify that the system detects it *, afterwards they will no longer be accessible.

* I have found that sometimes I have to disconnect and reconnect the iGalvanic for the system to detect the DAC, both.

 

1st PHASE:

 

1. Go to Start Menu >> Programs >> Audio Driver Control Panel, open the one we want to use.

2. Open Music Player

3. Open ProcessHacker:

                        

Go killing processes:

                        

                         fontdrvhost.exe (UMFD-0 instance)

                         lssas.exe

                         run32dll.exe

                         WinXShell.exe (smallest instance in kb)

 

PHASE 2: (continue with ProcessHacker)

                   

                        SUSPEND winlogon.exe (do not kill it)

                                                

Kill the following processes again, BY THIS ORDER:

                        

                        Pecmd.exe

                        WinXShell.exe (largest instance)

                        Processhacker.exe

 

Now we only have 12 active processes and 2 open applications (both audio), the player and the ASIO driver control panel.

We no longer have access to the browser or anything else, only the audio player. Only 4 active system services remain:

 

LSM (local session manager)

RpcEptMapper (RPC endpoint mapper)

DcomLaunch (DCOM Server Process Launcher)

RPC (remote procedure call)

 

Stopping any of them causes the collapse of the system, we are at the limit, the same happens with the number of processes, any of the 12 remaining that we close will cause the closure of windows or BSOD.

Closing the fontdrvhost.exe process (UMFD-1 instance) causes the loss of text from the browser windows, applications, etc. or their incorrect display, rendering them unusable. If we close WinXShell.exe before pecmd.exe, it launches it again, along with run32dll.exe.

To turn off or restart we must do it with the reset button or the PC off.

 

NOTE:

 

If the interface is the Explorer, we will have one more process, "dwm.exe", which we cannot kill. We will also have one more service, "CoreMessaging", which we will not be able to kill either.

Furthermore, WinXShell takes up less space than the Explorer interface.

It wouldn't have occurred to me to try it if it hadn't been done by Internethandle, to which I thank.

 

Greetings to all