Jump to content


Photo

Windows 11 PE Audiophile Creation Guide


  • Please log in to reply
703 replies to this topic

#1 samotc

samotc

    Die Hard

  • Members
  • PipPipPip
  • 201 posts
  • LocationSalamanca, Spain

Posted 26 November 2021 - 08:23 AM

Hello everyone, I finally finished the guide, I hope it will be useful for everyone who wants to build a Windows PE Audiophile, both 11 and 10, it is valid for both.
I have tried to make it easy to read and I intend that anyone with a little computer knowledge and who is not an expert, can build their own audiophile Windows PE.
Why windows PE as audio OS?
First of all, it takes up very little space, just over 1GB.
Second, it runs on RAM and only needs 2GB to run
Third, it runs with very few active processes and services, so most of the optimizations that are described in this, and other forums, already have them done, so the pending tasks are much less.
And a quarter; It sounds great, it has a great sound, even without tuning.
I encourage everyone to build one, 10, 11 or both, tune it up, and compare with what you have, and finally stick with the one you like best.
At the end of the day, what it is about is trying, experimenting and advancing in the achievement of our goals, neither more nor less than learning and enjoying music, and also learning.
I believe that all doubts and questions regarding the guide should be channeled through this thread, not through private messages, so we all learn.
A hug to all.

 

Attached Files


  • nik.d, Adrian, BernieK and 15 others like this

#2 Kuni

Kuni

    Die Hard

  • Members
  • PipPipPip
  • 257 posts

Posted 26 November 2021 - 10:19 AM

Great stuff ! I will try it right now and share later experiences. 


Audio PC Core 2016 AO2.0, SOTM, Gustard U16, DAC DIY, Pass Labs XA160, Wilson Audio Sasha v2, Speaker Silver cables DIY, Qyaide.


#3 samotc

samotc

    Die Hard

  • Members
  • PipPipPip
  • 201 posts
  • LocationSalamanca, Spain

Posted 26 November 2021 - 11:18 AM

I forgot to comment:
Automatic Minority Clean start:
mount VHD or USB Pen as drive X :, create shortcut of MinorityCleanxx.exe, copy to X:\Users \Default \AppData \Roaming \Microsoft \Windows \Start Menu \Programs \Startup, and it will start automatically, no need to install Sexe.exe.
It works on both Win11PE and Win10PE.


#4 internethandle

internethandle

    Die Hard

  • Members
  • PipPipPip
  • 280 posts

Posted 26 November 2021 - 07:17 PM

Very good job, thank you! I will be trying to create my own and compare with my stripped W10 soon.

Do you have an opinion on if Win11PE or Win10PE sounds better in your system?

#5 samotc

samotc

    Die Hard

  • Members
  • PipPipPip
  • 201 posts
  • LocationSalamanca, Spain

Posted 27 November 2021 - 05:43 AM

Personally, Win10XPE sounds better to me, it seems more musical to me, the 11 is colder and more analytical, it has less relief in the sound scene, it is like comparing a tube amp with an SS.
I like valves, I have a 320B XLS SE triode. In SS I have a Nelson Pass F5 + Nelson Pass BA3 Preamp, I think you will get an idea of the sound I like.
But, as I always say, do the 2 and compare, it does not take more than 2 hours, and with some practice 1 hour.
Stripping Windows PE is easier, there are fewer "clothes" to remove.


#6 internethandle

internethandle

    Die Hard

  • Members
  • PipPipPip
  • 280 posts

Posted 27 November 2021 - 04:00 PM

Thank you!

My system is currently all SS but for a number of years prior I was running tubes, so that is helpful. In truth, my stripped W10 is sounding a little too analytical with sharp transients and occasional harshness, so I may well play with W10PE to balance things out.

#7 samotc

samotc

    Die Hard

  • Members
  • PipPipPip
  • 201 posts
  • LocationSalamanca, Spain

Posted 28 November 2021 - 07:43 AM

Boot iso file Windows PE from system BCD:

 

Extract iso to a folder,

Copy boot.sdi file to a folder (SDI, NST .... or any other name) at the root of drive C:
Open Bootice.exe
Open "BCD" tab
Open tab "Easy Mode"
Create new entry "New WIM boot entry"
Select disk, partition where boot.wim is located
File: full path to boot.wim
SDI File: Full path to boot.sdi
Save Changes.
Get out,
 
Attached File  boot_iso_from_BCD system.jpg   98.78KB   89 downloads

  • rebone likes this

#8 internethandle

internethandle

    Die Hard

  • Members
  • PipPipPip
  • 280 posts

Posted 08 December 2021 - 09:33 PM

Am working on a stripped PE build thanks to samotc’s guide mixed in with some of my own methods. Stripping the flatboot has been a bit slow going (especially disabling services and drivers via the offline registry hives contained in the flatboot’s VHD and then testing to see what if anything breaks- it also took me some time to understand which files were missing that were causing TIDAL app to not playback in exclusive mode, but I managed to get it working after finding the missing files and migrating them from another non-PE host OS install) but PE sounds very good even “out of the box” and its ability to run with less (you can kill lsass.exe without issue, for instance!) has been very exciting.

About done stripping/disabling at this point and will post more thorough observations once I’m about finished and have things going.

Thank you to samotc!

#9 internethandle

internethandle

    Die Hard

  • Members
  • PipPipPip
  • 280 posts

Posted 12 December 2021 - 05:32 AM

samotc or others, would appreciate some help troubleshooting this issue:

- using samotc’s guide, I have successfully created a bootable Win10PE USB stick by creating an ISO with Win10XPE and then burning it to a USB thumb drive with Rufus. This USB stick boots into WinPE just fine.
- afterward, I’ve spent some time with a flatboot VHD, also with samotc’s guide, which also booted successfully after being added to my host OS’s boot menu and I’ve been able to edit registry settings and add programs etc. to my liking via this method, as samotc indicated in his guide.
- here is where I am running into trouble: using samotc’s guide’s method, I have converted the edited VHD’s contents back into a WIM format with DISM++, then replaced the original Win10XPE ISO’s boot.wim with the newly created WIM via UltraISO as samotc instructs, saving the new ISO, and loading it with Rufus onto a USB drive. However, when I reboot, the “Loading files” screen goes by with no issue, as well as the Windows logo and loading icon screen, but instead of proceeding to the configuration screen as it did in the original USB drive boot or in flatboot, it simply reboots back to POST.
- surprisingly, this does not seem to be due to something I did during editing the flatboot. I can have a completely unedited VHD with the contents of the originally created Win10XPE’s boot.WIM in it, convert that unedited VHD back to WIM, place that back into the ISO, load to USB, and the USB stick will still not load WinPE and instead reboot endlessly, so there seems to be something I am doing or not doing in the conversion between USB RAM disk boot to VHD and back that is causing the problem and not any edits I have made to the flatboot/VHD contents.

A user on the Win10XPE thread on tenforums seemed to think I needed to copy the original Win10XPE ISO file’s boot and efi folders back into the VHD contents before converting them back to WIM, but that did not resolve the issue. I am curious about whether they are right and it has something to do with the boot stores, but I have tried various combinations in Bootice with no resolution.

Thanks for any suggestions!

#10 samotc

samotc

    Die Hard

  • Members
  • PipPipPip
  • 201 posts
  • LocationSalamanca, Spain

Posted 12 December 2021 - 06:19 AM

When doing VHD >> WIM conversion with DISM ++ is the "bootable" box checked?
If not, check it.
Have you tried booting the WIM from the BCD System?

 

 

Boot iso file Windows PE from system BCD:

 

Extract iso to a folder,

Copy boot.sdi file to a folder (SDI, NST .... or any other name) at the root of drive C:
Open Bootice.exe
Open "BCD" tab
Open tab "Easy Mode"
Create new entry "New WIM boot entry"
Select disk, partition where boot.wim is located
File: full path to boot.wim
SDI File: Full path to boot.sdi
Save Changes.
Get out,
 

 


  • rebone likes this

#11 nik.d

nik.d

    Beginner

  • Members
  • 23 posts

Posted 12 December 2021 - 12:49 PM

Aside incorrect statements, please note that writing in upper case letters on forums means shouting. There's no reason to shout on anyone here. 



#12 internethandle

internethandle

    Die Hard

  • Members
  • PipPipPip
  • 280 posts

Posted 12 December 2021 - 09:31 PM

Well that sure was all something. 

 

Anyway,

 

 

When doing VHD >> WIM conversion with DISM ++ is the "bootable" box checked?
If not, check it.
Have you tried booting the WIM from the BCD System?

 

 

This worked! I knew it would be something minor I was overlooking. Thanks so much, was really giving me a headache.

 

To save others trouble, you need to have DISM++ in "Expert Mode" for the "Bootable" checkbox to be functional, apparently. It was greyed out before (unable to be checked or unchecked), but its default was checked so I assumed that it was being applied to the resultant WIM file outside of "expert mode," but it was not. You can tell if it is properly being applied because your WIM file will be significantly larger if it is not (e.g. a base Win10XPE created ISO for me was ~475MB, one with a boot.wim reconverted back with DISM++ without the "Bootable" box checked was ~600MB).

 

Thanks again!



#13 BernieK

BernieK

    Die Hard

  • Moderators
  • 1,717 posts
  • LocationMelbourne

Posted 13 December 2021 - 12:11 AM

 

 

Given your highly objectionable posts which contribute nothing of value to this discussion and apparently are intended only to create discord, the posts in question have been deleted and your ability to post on this Forum has been disabled.


  • NickD and Griddy99 like this

Control Point: Apple iPad (9th gen), 64Gb storage, 3Gb RAM, JPLAY for iOS 1.0.18; Samsung Galaxy Tab S6 Lite, 128Gb storage, 4Gb RAM, Bubble UPnP 4.3.3.1; Dell Inspiron 15 5510 laptop (Windows 11 Professional (x64) Version 22H2 (build 22621.3155), Intel Core i7-11390H, 2.93 GHz, 512Gb KIOXIA M2 PCIe NVMe (RAID) SSD, 16Gb DDR4 3200 MHz RAM), Upplay 1.7.1.

Control and Audio-PCs: Asus Mini PC PN60, Intel Core i5 8250U 1.6 GHz, 250Gb Kingston A2000 M2 NVMe SSD and 8Gb DDR4 2400 MHz RAM.

OS: Windows Server 2019 (Standard Edition) in highly optimized Desktop mode, command prompt shell for initial setup after which Control and Audio-PCs run headless (monitor, keyboard and mouse disconnected).
Optimization: Audiophile Optimizer 3.0, MajiorityCamisole 171 via TrustedClean 3.1b-server on RAM Disk in Audio PC (Local folder) (RAM Disk procedure and TC settings used are detailed in this guide - 8 Nov 2023), Process Lasso Server Edition 14.0.2.12, additional Windows processes/services stopped via registry editor, task manager and a modified CAD DSK script. For the full optimization procedure see my Guide for Optimizing WS2019 in a Dual or Single PC JPLAY Femto-Based System (revised 5 July 2023).

Renderer: JPLAY FEMTO 7.0D UPnP (Alternative version), Server: JPLAY FEMTO 7.0D femtoServer, File Manager: Q-Dir 11.5.5.0, Library Manager: JRiver MC 32.0.6.
JPLAY Settings: Playing via: KS, Engine: ULTRAstream, Bitstream: Native, Bitperfect Volume: OFF, DAC Link: 1000, XtreamSize: 1000, Throttle: ON, Hibernate Mode: ON.

Equipment Configuration: Control Point Tablet/Laptop > WiFi > Control-PC > 1m SUPRA Cat 8 Ethernet Cable > Audio-PC > 3m Chord C-USB Cable > Rotel 1590C > 2m Mogami NEGLEX RCA to XLR cable with Neutrik connectors) > March Audio P501 Monoblocks with Purifi 1ET7040SA modules > DIY speaker cables (Tycab PVC doubly insulated 11 AWG OFC wire, TechFlex braid, Neotech Banana/Spade connectors) > Bryston PX-1 external crossovers > DIY speaker cables (as before) > Bryston Model T Signature Speakers. AC power filtered/cleaned via Thor A12BF Smart Power Board. 

Music Storage: Main Library: 6Tb Seagate HDD/Hub+6Tb Seagate HDD (all connections via 0.5m Avencore Premium USB 3.0 cables); Backups (x2): as per Main Library.


#14 samotc

samotc

    Die Hard

  • Members
  • PipPipPip
  • 201 posts
  • LocationSalamanca, Spain

Posted 13 December 2021 - 07:03 AM

Well that sure was all something. 

 

Anyway,

 

 

This worked! I knew it would be something minor I was overlooking. Thanks so much, was really giving me a headache.

 

To save others trouble, you need to have DISM++ in "Expert Mode" for the "Bootable" checkbox to be functional, apparently. It was greyed out before (unable to be checked or unchecked), but its default was checked so I assumed that it was being applied to the resultant WIM file outside of "expert mode," but it was not. You can tell if it is properly being applied because your WIM file will be significantly larger if it is not (e.g. a base Win10XPE created ISO for me was ~475MB, one with a boot.wim reconverted back with DISM++ without the "Bootable" box checked was ~600MB).

 

Thanks again!

 

In the end how does it boot, from usb or from bcd?
I do it from BCD, for me it is more comfortable than booting from the BIOS start menu, and faster.
Tell us what you think about the sound of WinPE compared to Windows 10 stripped down.
The most interesting would be Win10 without stripping against Win10XPE under the same conditions, the comparison will be more equitable.
 

 



#15 samotc

samotc

    Die Hard

  • Members
  • PipPipPip
  • 201 posts
  • LocationSalamanca, Spain

Posted 13 December 2021 - 07:48 AM

I apologize for having overlooked in the guide, the detail that DISM ++ must always run in EXPERT MODE, I have been using it like this for so long that I had not realized the matter.
It is possible that Bobo's problem was that.


#16 Marcin_gps

Marcin_gps

    JPLAY & JCAT Founder

  • Administrators
  • 4,305 posts

Posted 13 December 2021 - 09:17 AM

Guys, markoliver is banned.

 

Regards, 

Marcin


JPLAY for iOS: the new reference hi-fi app. 


JCAT: streaming specific products for high-end audio
 
Join Computer Audio Enthusiasts group on facebook

#17 internethandle

internethandle

    Die Hard

  • Members
  • PipPipPip
  • 280 posts

Posted 13 December 2021 - 04:52 PM

At the moment I’m booting it from USB. Part of my goal would be to disconnect all of my SATA drives and disable the SATA ports in BIOS (even with a SOtM SATA filter and a Paul Pang SATA cable, SATA drives are pretty noisy, plus of course the higher latency vs RAM).

I still am stripping/playing with registry edits and disabling for the Win10PE build, but I am pretty close. Last night, for instance, I discovered I could disable and delete “vdrvroot” and “storahci” for USB boot (but not flatboot, these are related to both VHD and SATA AHCI mode), so now I’m looking to see what else USB boot will allow vs flatboot and vice versa. Also, I noticed that programs such as Process Hacker will allow you to set processor and I/o priority and affinity for processes that normal W10 would give you a access denied error for (e.g. csrss.exe and services.exe) - very cool!

I will report back! :)

#18 kalaha777

kalaha777

    Beginner

  • Members
  • 4 posts

Posted 15 December 2021 - 11:38 AM

Thank you very much for your hard work and the opportunity to get in touch with win10pe audio. I was fascinated by the ability to edit win10-11 for myself. I have been looking for this information for a long time. I am not in an English-speaking country, I apologize for the mistakes in the letter. With win10PE, the first experience, so you have to collect everything by kerpichek. Faced such a difficulty: 1) When creating a flat boot, you need the main 3-programs: WinNTSetup; Dism ++ (not a working link, maybe in my country; Bootice all of them (contained in Windows PE Strelec); How to make WinPE Strelec work on a created and running win10 pro image. Perhaps WinPE Strelec can be edited too, but I don't know how to do it . WinPE Strelec do you recommend as a source of these programs, how to make it work with edited win10pro? I tried to pull these programs out of the WinPE Strelec image but DISM ++ refused to work correctly. 2) How to return brightness control to a laptop, it is hard to work when it is on maximum? 3) After creating the win10pro image, I lost the Internet (via the cable), and I wanted to return the system simple sounds. Correct if something is wrong.

#19 internethandle

internethandle

    Die Hard

  • Members
  • PipPipPip
  • 280 posts

Posted 16 December 2021 - 03:00 AM

Hello kalaha777,

i have just finished making a custom WinPE ISO of my own using samotc's guide primarily and am very much enjoying the sound. Because I just finished, I am pretty familiar with the process and will try to help you:

The WinPE Strelec is a pre-made customized WinPE ISO made by another person that contains a lot of recovery software and other software. I did not use it, I just downloaded the programs that samotc recommended from the internet (WinNTSetup, DISM++, Bootice, Rufus, RegistryChangesView, UltraISO, and others). The only program that is not available elsewhere that is included in the WinPE Strelec is "Remote Registry," but you can use another registry editor program on another running Windows 10 Pro image, load the hives from the VHD of the flatboot of WinPE (located in Windows\system32\config -- the two relevant hives are "SOFTWARE" and "SYSTEM") and then unload them when done editing the VHD flatboot registry. If you want to use the WinPE Strelec instead, you would need to load it onto a USB drive or its own VHD/flatboot, and boot from it, then work on the VHD flatboot by mounting it from within WinPE Strelec. I am unsure why DISM++ is not able to extract the programs from within the images files for WinPE Strelec, but WinPE Strelec is so heavily modified that may be the reason.

For the brightness control, I am unsure, it would be dependent on whether it is a setting in your laptop's hardware or not. Unfortunately, "PeCMD.exe" and "FixScreen.exe," which are related to display settings, have limited functionality in WinPE vs. Win10’s full display settings, so if the brightness control is located in Windows, you may have some trouble. You could try adding your normal graphics drivers (Intel or NVIDIA or whatever is your normal GPU drivers) to WinPE in the Win10XPE program before making the WinPE ISO. For the system simple sounds and ethernet settings, the same would apply -- there are checkboxes in Win10XPE for including system sounds, as well as for network drivers. If the "PENetwork" software included does not work for your ethernet connection, you can try the option to "add host network drivers" in Win10XPE, which is what I did to allow my JCAT FEMTO Ethernet card to work. This way, I do not have to use the PENetwork software, and do not include it in my Win10XPE created ISO.

I hope this helps.

I will be following up this post with a more detailed impressions post as well as some more thoughts about the process of creating the ISO.
  • rebone likes this

#20 samotc

samotc

    Die Hard

  • Members
  • PipPipPip
  • 201 posts
  • LocationSalamanca, Spain

Posted 16 December 2021 - 11:58 AM

If the link referring to DISM ++ does not work for you, do a search in google and many will appear, I suppose that some will be functional.
I only use Strelec for the Remote Registry, the rest of the programs I use from my main OS (Windows Server 2019)
Ultraiso I have it registered, I don't know if in demo mode it will work completely.
Regarding the brightness of the screen, from what I have seen in the file "pecmd.ini" it only contemplates the screen resolution, I am afraid that it will not help you there.
Strelec is very difficult to edit since its structure is heavily modified, in fact it contains several .wim files referred to in its BCD, you can see it by editing the Strelec BCD with Bootice >> Easy Mode.
I think with the above programs installed on your host you should have no problem getting a Win10XPE Audio or any other, greetings.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users