728 replies to this topic

[samotc]

@Internethandle

 

Another alternative, should this fail, would be to try to load audioserv and AudioEndpointBuilder with pecmd.ini., as reflected in the _SUB AudioInit section:

 

//SERV -wait Audiosrv (audio service already started)

// Install HDAudio driver sound cards

DEVI %WinDir%\inf\hdaudio.inf

WAIT 250

 

// Adjust the volume (windows default 67%) ex: 65535*33% = 21626 (Uncommented if mute is not selected). Volume changed according to "System Volume At Startup" interface value

EXEC=!%WinDir%\System32\nircmd.exe setsysvolume 21626

 

// Play Startup sound (Commented if mute is selected)

EXEC @!%WinDir%\System32\mpg123.exe -q %SystemRoot%\Media\startup.mp3

 

// Start NonVisual Desktop Access after Audio (Uncommented By NVDA Plugin)

//EXEC @!%WinDir%\System32\NVDA_Startup.cmd

 

Keep in mind that to start Ultralite with pecmd.exe/pecmd.ini you must modify the registry by changing the key HKLM\SYSTEM\SETUP\CmdLine: "winpeshl" to "Pecmd.exe Main %Windir%\system32\Pecmd.ini"

 

Good luck and be useful, best regards

[seeteeyou]

If we weren't really getting anywhere with WASAPI whatsoever, hopefully something like this would be somewhat helpful.

 

As I mentioned before, quite a few lists of packages were created while we're focusing on winpe.txt (i.e. Ultralite version from a6296c5a6eec9ca02b431ed0461b952d.cab) and winre.txt (i.e. \Windows\Recovery\winre.wim extracted from sources\install.wim) right now.

 

 

 

Only 6 out of 409 packages should have something to do with audio according to winpe.txt

 

https://github.com/s...e.txt#L404-L409

Spoiler

Multimedia-AudioDriversCore-Package~31bf3856ad364e35~amd64~en-US~10.0.22000.1.mum
Multimedia-AudioDriversCore-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum
Multimedia-MMECoreBase-Full-Package~31bf3856ad364e35~amd64~en-US~10.0.22000.1.mum
Multimedia-MMECoreBase-Full-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum
Multimedia-MMECoreBase-Package~31bf3856ad364e35~amd64~en-US~10.0.22000.1.mum
Multimedia-MMECoreBase-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum

 

 

 

Then we'll take a look at winre.txt and 2 extra packages were found

 

https://github.com/s...e.txt#L452-L459

Spoiler

Multimedia-AudioDriversCore-Package~31bf3856ad364e35~amd64~en-US~10.0.22000.1.mum
Multimedia-AudioDriversCore-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum
Multimedia-MMECoreBase-Full-Package~31bf3856ad364e35~amd64~en-US~10.0.22000.1.mum
Multimedia-MMECoreBase-Full-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum
Multimedia-MMECoreBase-Package~31bf3856ad364e35~amd64~en-US~10.0.22000.1.mum
Multimedia-MMECoreBase-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum
Multimedia-MMECoreWdmAudio-Package~31bf3856ad364e35~amd64~en-US~10.0.22000.1.mum
Multimedia-MMECoreWdmAudio-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum

 

Besides, winre.txt was also showing 8 additional packages that could be useful

 

https://github.com/s...e.txt#L391-L398

Spoiler

Microsoft-Windows-WinPE-AudioCore-merged-Package~31bf3856ad364e35~amd64~en-US~10.0.22000.1.mum
Microsoft-Windows-WinPE-AudioCore-merged-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum
Microsoft-Windows-WinPE-AudioCore-Package~31bf3856ad364e35~amd64~en-US~10.0.22000.1.mum
Microsoft-Windows-WinPE-AudioCore-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum
Microsoft-Windows-WinPE-AudioDrivers-merged-Package~31bf3856ad364e35~amd64~en-US~10.0.22000.1.mum
Microsoft-Windows-WinPE-AudioDrivers-merged-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum
Microsoft-Windows-WinPE-AudioDrivers-Package~31bf3856ad364e35~amd64~en-US~10.0.22000.1.mum
Microsoft-Windows-WinPE-AudioDrivers-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum

 

Finally 4 more packages from winre.txt were found

 

https://github.com/s...e.txt#L464-L467

Spoiler

WinPE-AudioCore-Package~31bf3856ad364e35~amd64~en-US~10.0.22000.1.mum
WinPE-AudioCore-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum
WinPE-AudioDrivers-Package~31bf3856ad364e35~amd64~en-US~10.0.22000.1.mum
WinPE-AudioDrivers-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum

 

 

 

In other words, there were only 6 packages from winpe.txt and then 8 + 8 + 4 = 20 packages from winre.txt respectively.

 

Let's see if we're able to extract those 20 - 6 = 14 packages from winre.txt and then add them to winpe.txt afterwards.

 

[seeteeyou]

Maybe here's why we're having better luck with WASAPI when the image was created by Win10XPE

 

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

As Win10XPE is based upon WinRE... We have had no issues with using the Basic MS - Display, Audio, Wifi, Ethernet, Storage, etc. Drivers included with Windows.........

 

That means we could consider this as an alternative

 

https://gist.github....e0f5debb2c458e6

Find winre.wim in C:\Recovery\WindowsRE\ OR C:\Windows\System32\Recovery\ and paste it as boot.wim.

 

Then we'll take advantage of this afterwards

 

https://github.com/h...releases/latest

https://forums.mydig...t/posts/1342123

I was unable to download NSudo, so i download ExecTI & cbsenum-0.9, they work just fine together.

 

Uninstalled all the crap i wanted to, just fine.

 

[samotc]

 

I have removed F2k, BugHead, DSDTranscoder, and the ASIO drivers (DIYNHK and IFIUSBAUDIO), and the resulting size of the Win11 PE_MINIMAL boot.wim is 93.4 MB, so I think the goal of getting below 100 MB is achieved.

Reflecting a bit, I'm wondering why Windows has to be so big (Windows 11 "Normal" occupies almost 30 GB) when with only 93.4 MB it can work?

why is this ms windows policy getting more bloated?

Not only for audio, I have also built a "rescue" one with MS Office 2007 installed and network printing support, VideoLan, and other apps and utilities, some installed, not portable, . which does not occupy more than 600 MB.

After all, an OS should only be built to run applications, it is a means, not an end in itself.

Therefore, we only need the OS that runs the applications we want to use, and if possible with the minimum possible size (less consumption of resources, memory, disk, CPU...)

  I think that with the idea and in the end the construction of PE Audiophile, many doors have been opened, and each one will decide whether to cross them or not, to see what is behind them.

Greetings to all.

[ts8]

Do you know that US military in the 50s have began with an armoured personal carrier and ended up with a big gun tank with wings!

Truly American style!

[seeteeyou]

Here's a (long) list of reasons why we should stay away from bloated Windows 10 / 11 / Server etc.

 

Spoiler

https://privacy.micr...sonaldatamodule

Finally, we will retain, access, transfer, disclose, and preserve personal data, including your content (such as the content of your emails in Outlook.com, or files in private folders on OneDrive), when we have a good faith belief that doing so is necessary to do any of the following:

• Comply with applicable law or respond to valid legal process, including from law enforcement or other government agencies.

 

Microsoft covertly collects personal data from enterprise Office ProPlus users

https://www.csoonlin...plus-users.html

 

Dutch audit finds Microsoft Office leaks confidential data

https://www.computer...nfidential-data

 

Windows 10 telemetry secrets: Where, when, and why Microsoft collects your data

https://www.zdnet.co...emetry-secrets/

 

Microsoft walks a thin line between Windows 10 telemetry and snooping

https://www.computer...d-snooping.html

 

New Windows 7 'security-only' update installs telemetry/snooping, uh, feature

https://www.computer...uh-feature.html

 

For real Windows 10 privacy, you need the China Government Edition

https://www.computer...nt-edition.html

Because Windows doesn’t make much money for Microsoft these days, the company decided, beginning in Windows 10, that snooping on users à la Google and Facebook could be profitable. But one country said enough was enough. It would stand up for its users’ “privacy.” That country? The People’s Republic of China.

 

Cough. Didn’t see that one coming, did you?

 

https://seekingalpha...ust-bought-time

On May 23th, in the Eastern city of Shanghai, Microsoft (NYSE: NASDAQ:MSFT) quietly released what is probably the best version of Windows since Windows 7. Its name, Windows 10 China Government Edition.

 

Windows 10 China Government Edition is a collaboration between China Electronics Technology Group (CETC), a Chinese state-run technology and defense company, and Microsoft to develop a version of Windows that complies with governmental standards with respect to privacy and security.

 

In particular, this version strips telemetry and data collection from Windows; thus, in a bit of irony, the Chinese Government-mandated edition is the only version of Windows since XP (or Windows 7 before updates/patches) that respects the privacy rights of its users and is not, as of today, a data-collection machine.

 

 

 

Worst Windows 10 version ever? Microsoft's terrible, horrible, no good, very bad October

https://www.zdnet.co...ry-bad-october/

But telemetry fails miserably at detecting anything that isn't a crash or an unambiguous failure. In theory, those low-volume, high-impact issues should be flagged by members of the Windows Insider Program in the Feedback Hub. And indeed, there were multiple bug reports from members of the Windows Insider Program, over a period of several months, flagging the issue that caused data to be lost during some upgrades. There were also multiple reports that should have caught the Zip file issue before it was released.

 

Microsoft halts rollout of Windows 10 October 2018 Update: What happens next?

https://www.zdnet.co...t-happens-next/

This morning, I searched through Microsoft's Feedback Hub app, where Windows 10 users can provide bug reports and feature requests for both previews and released builds. A quick search revealed multiple examples of users reporting issues with deleted files.

 

One report from three months ago was headed "Files deleted!!!!" and noted that after installing a preview release "my Documents folder had been overwritten with a new Documents folder, complete with custom icon. All contents were gone."

 

https://archive.today/V6AyO

Sampling of Feedback Hub reports of data deletion from as early as 3 months ago

 

 

https://twitter.com/...535774088581120

DUDE. I just got perma banned from /r/Windows10 instantly for posting this link. What the hell? No reason. asked why. no response for 10 mins

 

 

Feedback hub did it's job - 'ignored the feedbacks'

https://www.reddit.c..._the_feedbacks/

 

Cumulative Update bugs spur Microsoft to call for help. Where’s the telemetry when we need it?

https://www.computer...we-need-it.html

 

Microsoft seeks enterprise help in optional OS update testing

https://www.techcent...update-testing/

 

Microsoft to business: Don't worry about Windows 10, consumers will test it

https://www.computer...ll-test-it.html

 

Microsoft Admits Normal Windows 10 Users Are 'Testing' Unstable Updates

https://www.forbes.c...stable-updates/

 

Microsoft's reduced emphasis on QA testing

https://4sysops.com/...s-on-qa-testing

 

Why Microsoft is using Windows customers as guinea pigs – Reply to Tim Warner

https://4sysops.com/...-to-tim-warner/

 

Windows 10 Enterprise updates turn consumers into guinea pigs

https://www.techrada...ea-pigs-1296646

 

Microsoft Bug Testers Unionized. Then They Were Dismissed

https://web.archive....-were-dismissed

https://www.warren.s...Deal.pdf#page=5

https://crsreports.c...47203/2#page=11

 

Former Microsoft Employee explains why bugs in Windows updates increased

https://www.ghacks.n...ates-increased/

The main sources of testing data, apart from the automated test systems that are in place, comes from Telemetry and Windows Insiders. Windows Insider builds are installed on millions of devices and Microsoft collects Telemetry from all of these devices.

 

If something crashes, Microsoft gets information about it. One of the issues associated with the collecting of Telemetry is that most bugs are not caught by it. If something does not work right, Microsoft may not be able to discern the relevant bits from Telemetry data. While it is in theory possible that users report issues, many don't and at other times, issues may go under because of other feedback that Microsoft gets from Insiders. Additionally, while Insiders may report bugs, it is often the case that necessary information is not supplied to Microsoft which poses huge issues for the engineers tasked with resolving these issues.

 

Back in 2014/2015, Microsoft's Testing team would be tasked with analyzing bugs and issues, and supplying engineers with the data they required to resolve these. Nowadays, Berg notes, it is Telemetry that the engineers look at to figure out how to fix these issues and fixes are then pushed to customer devices running Insider Builds again to see if the issue got fixed or if it created new bugs.

 

Microsoft crowdsourced QA, and look what we got

https://www.computer...hat-we-got.html

Microsoft says Insiders have helped make sure that Windows runs better and more reliably than ever by finding bugs early — which, when you think about it, is an odd statement. It almost sounds as if Microsoft is saying that before Windows Insiders was established, it just shipped out updates without any testing at all: Good luck, world!

 

But of course, that’s not what it did. Before 2014, Microsoft had a team devoted to testing Windows in real-world situations and analyzing the results. That year, it started testing Windows on virtual machines, says Jerry Berg, a Microsoft senior software development engineer for testing who was on the team and worked at the company for 15 years. The VMs didn’t work as well, it found — but it didn’t bring back the team.

 

Over 10 Million People Now Help Microsoft Make Windows 10 Bug-Free, for Free

https://wccftech.com...indows-10-free/

Microsoft has also been accused of using Windows 10 testers as free workers as it laid off much of its internal testing team. But whatever the concerns, the program is definitely a success giving Insiders and the public an early look at the upcoming features, along with giving them a chance to push the company to focus on some specific feature or improvement.

 

https://www.linkedin...oft-yusuf-mehdi

We count over 10M Windows Insiders today, many of them fans, who test and use the latest build of Windows 10 on a daily basis. Their feedback comes fast and furious, they have a relentless bar of what they expect, but it so inspires our team and drives our very focus on a daily basis.

 

Microsoft admits non-insiders are beta testing Windows updates

https://www.techspot...ws-updates.html

Windows Insiders apparently not providing enough information

 

Software quality sucks – what are you going to do about it?

https://www.cio.com/...o-about-it.html

As software companies become slaves to speedy releases, and QA testers have been left in the dust, consumers are the ones left dealing with the crappy code that gets delivered.

 

We could always keep going with that list, though it's gonna get quite boring after a little while IMHO.

 

The entire situation should be way beyond ridiculous to say the least, that's why both Senate and Congress were pointing their fingers at Micro$oft after Bloomberg reported that QA testers were getting the pink slip.

 

A former employee explained everything in details:

 

https://www.youtube....h?v=S9kn8_oztsA

 

In other words, we're always handed the short end of the stick on a silver platter. Apparently we're treated more like lab rats since they've got 10 millions (and counting?) of beta testers for absolutely free. Not to mention the fact that we're being spied on thanks to the gift that keeps on giving called Telemetry.

 

Heck, no Telemetry whatsoever if we're running Windows PE on a daily basis. I guess that's the whole point of learning more about how to build our own version of PE then?

 

 

 

They've got tons of Features on Demand (FODs) in addition to their Inbox Apps.

 

Stuff like .NET Framework and PowerShell etc. would also occupy some space.

 

Lots of device drivers were bundled by default, though they're supposed to be relatively small to begin with.

 

Then we've got Windows Update each and every month, the size of WinSxS would keep growing for obvious reasons.

[robpisa]

@seeteeyou

 

This tool cbsenum that you pointed seems to be amazing, as it is a sort of packet manager for Windows like in Linux (and it written in Pascal....).

 

My understand that it should help a lot to reduce WinSxS. Are you aware of a similar tool to reduce SysWOW64?

 

Thanks you

-R

 

P.S. It seems so, I missed your previous post #446

 

Then we'll take advantage of this afterwards

 

https://github.com/h...releases/latest

 

 

[seeteeyou]

@robpisa

 

Yes, that's exactly how they're getting things done these days

 

https://github.com/h...cbsenum#cbsenum

Component-Based Servicing is a technology since Windows Vista which most resembles Linux-style package managers. It builds upon WinSxS (Side by side assemblies) to allow installation, deinstallation and updating of numerous Windows components independently.

 

It presents a moderately componentized view into Windows and allows uninstalling parts of system which outside of Windows Embedded were previously seen as monolithic.

 

In Windows, this technology is hidden from general public. There's a command-line tool dism.exe to manage CBS packages, but most packages are marked as hidden even from DISM.

 

Basically it's pretty much like the GUI version of this, just a matter of unhiding lots of packages or else we wouldn't be able to touch them in the first place

 

https://github.com/s..._registry_tweak

https://msfn.org/boa..._registry_tweak

https://www.wincert....ll_wim_tweakexe

 

 

 

Windows Package Manager

https://learn.micros...ackage-manager/

 

Windows Package Manager CLI (aka winget)

https://github.com/m...soft/winget-cli

 

WingetUI: A GUI for Winget, Scoop and Chocolatey

https://github.com/m...liment/WingetUI

https://www.marticliment.com/wingetui/

 

NuGet documentation

https://learn.micros...om/en-us/nuget/

 

Client Tools for NuGet

https://github.com/NuGet/NuGet.Client

 

They also have separate package management systems for other software categories as shown above, while CBS should be meant for their built-in packages.

 

 

 

For UWP-related (Universal Windows Platform) packages that could be found on their official Microsoft Store, usually we could get them manually like this

 

https://store.rg-adguard.net

https://gbatemp.net/...toreweb.574475/

https://github.com/G...011/GetStoreApp

https://github.com/s...88/XboxDownload

https://github.com/S...reWeb/issues/14

 

Language and Optional Features (i.e. Features on Demand) as well as Inbox Apps could be found on either UUP dump or extracted from official ISO images

 

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

https://learn.micros...ks#requirements

 

Now we know why Windows 10 / 11 / Server etc. would be such a heavyweight champion

 

http://morganspurloc.../super-size-me/

 

http://morganspurloc...2-holy-chicken/

 

https://www.nhlbi.ni...ents/matte1.htm

 

 

 

Whenever we could find any packages with WOW64, they should be removed from that SysWOW64 folder after unininstalling them with CBSEnum.

 

We could notice the difference by taking a look at the following example

 

https://github.com/s...npe.txt#L33-L36

Microsoft-ClientCore-Pnp-Desktop-Package~31bf3856ad364e35~amd64~en-US~10.0.22000.1.mum
Microsoft-ClientCore-Pnp-Desktop-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum
Microsoft-ClientCore-Pnp-Package~31bf3856ad364e35~amd64~en-US~10.0.22000.1.mum
Microsoft-ClientCore-Pnp-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum

https://github.com/s...npe.txt#L37-L38

Microsoft-ClientCore-Pnp-WOW64-Package~31bf3856ad364e35~amd64~en-US~10.0.22000.1.mum
Microsoft-ClientCore-Pnp-WOW64-Package~31bf3856ad364e35~amd64~~10.0.22000.1.mum

 

[robpisa]

Thank you seeteeyou, very helpful!

-R

 

P.S. Now I understand, winget reminds me apt-get under Linux

 

 

@robpisa

 

Yes, that's exactly how they're getting things done these days

 

[...]

[Jack7878]

我正在寻找英文版的 Windows 10 LTSC 2019 Build 17763.3653 Update 2022-11，我只能找到中文版。

关于如何从微软服务器下载它的任何想法？

I am also looking for Windows 10 LTSC 2019 Build 17763.3653 Update 2022-11 in English, please let me know if you find it, and there is also ChatGPT in English, I am also looking for

[seeteeyou]

Even the size of each and every official Windows PE version just kept growing over the years, that's only under 200MB back in 2006 while it's getting very close to 300MB in 2023.

 

 

Vista RTM = 177,433,060 bytes

https://archive.org/...5.iso/WINPE.CAB

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2006-11-02 08:42:22 ....A    177433060               F3_WINPE.WIM

 

Vista SP1 = 201,179,410 bytes

curl -N -r 519776256-1176507204 -o winpe.cab https://download.microsoft.com/download/9/c/d/9cdfa30e-5901-40e4-b6bf-4a0086ea0a6a/6001.18000.080118-1840-kb3aikl_en.iso

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2008-01-23 10:04:32 ....A    201179410               F3_WINPE.WIM

 

7 RTM = 135,115,506 bytes 

curl -N -r 640526336-1086964920 -o WinPE.cab https://download.microsoft.com/download/8/E/9/8E9BBC64-E6F8-457C-9B8D-F6C9A16E6D6A/KB3AIK_EN.iso

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2009-07-13 20:13:34 ....A    135115506               F3_WINPE.WIM

 

7 SP1 = 135,464,046 bytes 

curl -N -r 1548288-137012333 -o WINPE.WIM https://download.microsoft.com/download/0/4/C/04C805CC-4C04-4D76-BE80-7D67B951CF73/waik_supplement_en-us.iso

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2010-11-20 16:15:44 .....    135464046               AMD64\WINPE.WIM

 

8 = 165,629,257 bytes

https://archive.org/...f1416062098.cab

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2012-07-25 23:26:18 ....A    165629257               filad61cf00c94775125d186add4ac43371

 

8.1 = 176,787,265 bytes

https://archive.org/...f1416062098.cab

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2013-08-22 07:02:24 ....A    176787265               filad61cf00c94775125d186add4ac43371

 

1507 = 217,370,903 bytes

https://web.archive....f1416062098.cab

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2015-07-10 04:32:00 ....A    217370903               filad61cf00c94775125d186add4ac43371

 

1511 = 212,505,063 bytes

https://web.archive....f1416062098.cab

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2015-10-30 00:16:18 ....A    212505063               filad61cf00c94775125d186add4ac43371

 

1607 = 222,718,557 bytes

https://download.mic...f1416062098.cab  

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2016-07-16 05:41:02 ....A    222718557               filad61cf00c94775125d186add4ac43371

 

1703 = 234,670,849 bytes

https://download.mic...f1416062098.cab

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2017-03-18 14:46:26 ....A    234670849               filad61cf00c94775125d186add4ac43371

 

1709 = 244,737,938 bytes

https://download.mic...f1416062098.cab

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2017-09-29 06:39:34 ....A    244737938               filad61cf00c94775125d186add4ac43371

 

1803 = 252,250,630 bytes

https://download.mic...f1416062098.cab

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2018-04-11 15:14:36 ....A    252250630               filad61cf00c94775125d186add4ac43371

 

1809 = 263,406,883 bytes

https://download.mic...f1416062098.cab

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2018-09-14 23:39:36 ....A    263406883               filad61cf00c94775125d186add4ac43371

 

1903 = 264,950,382 bytes

https://download.mic...f1416062098.cab

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2019-03-18 20:57:34 ....A    264950382               filad61cf00c94775125d186add4ac43371

 

2004 = 267,703,373 bytes

https://download.mic...f1416062098.cab

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2019-12-06 22:58:34 ....A    267703373               filad61cf00c94775125d186add4ac43371

 

Server 2022 = 291,185,961 bytes

https://download.mic...ed0461b952d.cab

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2021-05-08 01:56:50 ....A    291185961               filad61cf00c94775125d186add4ac43371

 

11 21H2 = 297,338,184 bytes

https://download.mic...ed0461b952d.cab

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2021-06-05 05:34:22 ....A    297338184               filad61cf00c94775125d186add4ac43371

 

11 22H2 = 303,300,539 bytes

https://download.mic...ed0461b952d.cab

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2022-05-06 22:39:18 ....A    303300539               filad61cf00c94775125d186add4ac43371

 

Validation OS = 195,506,152 bytes

curl -N -r 729088-196235239 -o ValidationOS.wim https://software-static.download.prss.microsoft.com/dbazure/888969d5-f34g-4e03-ac9d-1f9786c66749/22621.1.220506-1250.ni_release_amd64fre_en-us_VALIDATIONOS.iso

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2022-05-07 05:57:44 .....    195506152               ValidationOS.wim

 

11 Insider Preview 25309 = 310,709,881 bytes

curl -N -r 1269383168-1579186954 -o a6296c5a6eec9ca02b431ed0461b952d.cab https://opendirectory.luzea.de/Enthousiast/25309_IP_TB_KiTS/Windows_Preinstallation_Environment_en-us_25309.iso

   Date      Time    Attr         Size   Compressed  Name
------------------- ----- ------------ ------------  ------------------------
2023-02-25 11:02:30 ....A    310709881               filad61cf00c94775125d186add4ac43371

 

 

Thankfully we could still get that reduced so it's actually less than 100MB these days.

[samotc]

SOME THOUGHTS ABOUT WIN11 PE MINIMAL AUDIO:

 

First of all, I want to mention my surprise at the difference in sound when booting the usb flashdrive in Ventoy mode (ISO to RAM or WIM) Grub4DOS (ISO to RAM) and Windows BCD (WIM)

 

By far the best-sounding is the G4D, then BCD Windows, and finally Ventoy (sounds downright awful).

 

Another fact that I have verified is that the difference between F2k and BH (Infinity Blade) is very small, always in favor of Infinity Blade, but I have updated the Bass libraries that this program contains, and the improvement has been very evident, now Infinity Blade sounds much better than F2k.

The dlls of the bass library can be downloaded from here:

https://www.un4seen.com/

Anyway, I don't understand why these differences between G4D, BCD, and Ventoy, nor why the latter sounds so bad.

Regards.

[zaurux]

I am thinking of upgrading my audio server (i7 12th generation) and therefore reinstalling a system.

My W10 LTSC is very optimized and works very well (30 processes, low latency, etc...).

I can start again on the same basis but this WinPE interests me.

 

On the other hand, to take the 29 pages, I got lost several times...

So, it is not possible to have a simple image to install on a key, a basic howto to add Roon, HQPlayer, Processlasso, Minority, TightVNC... and that's all !!! ...    uh, no,  Totalcommander & Run-Command, too !!

[mos777]

samotc Hello! Can you tell me where in our larger thread there was a detailed discussion how to do it of G4D to RAM ? And what version of BH are you using?

[samotc]

@ mos777:

 

1. Answering your first question:

 

Passing ISO to RAM is very easy.

 

A. Install G4D on the USB flashdrive that we want to use.

B. Copy the files grldr and grldr.mbr (contained in the program folder) to the root of the USB flashdrive

C. Open a text editor (notepad or other) and add the following:

 

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

timeout nn

default /default

 

title WINDOWS 11 PE AUDIO MINIMAL ISO TO RAM

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

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

map --hook

chainloader (0xff)

 

Once this is done, save the file as menu.lst in the root of the USB, the ISO file here is in the root of the USB, if it is in another place, put the full path to where the ISO file is located.

 

nn is the time in seconds you want it to wait before booting.

 

I recommend this version: grub4dos-0.4.6a-2021-08-13

It can be downloaded from here:

 

https://github.com/chenall/grub4dos.

 

It can also be done with flatboot.vhd, but it requires installing the signed SVBus drivers, and it doesn't provide any advantage, not sonic either.

 

2. In response to your second question:

 

I use BH 7.27, it's very old, but I've tried others, and I like them less. I use it in portable mode and with the minimum to work, only Infinity Blade and the bass libraries, and the *.dat files of the application, I deleted everything else.

 

I hope it works for you, greetings.

 

NOTE: Remember that G4D only works on MBR and BIOS/CSM.

You have to format the flash drive in NTFS/FAT32 as a PRIMARY and ACTIVE partition.

[seeteeyou]

FYI - older versions of BH could still be found on Google Drive and all credits go to the author of his original forum post AntonKhonin

 

https://forum.doctor...comment-1135824

 

If we weren't brought to the exact forum post linked above, simply look for Опубликовано 29 сентября, 2019 (i.e. 29 September, 2019) on page 302 instead.

 

 

 

I already verified the hash value of BH 7.27 (i.e. package_20160616_Bughead_x64.zip) available on Google Drive, fortunately it's a perfect match when compared to what the developer posted back in 2016

 

https://www.my-hiend...2973#post252973

https://www.purebasi...=489883#p489883

https://web.archive....can.jp/bughead/

 

 

 

Direct links to download the latest BASS audio library

 

https://www.un4seen....iles/bass24.zip

https://www.un4seen..../bassalac24.zip

https://www.un4seen....s/bassape24.zip

https://www.un4seen..../bassasio14.zip

https://www.un4seen....es/basscd24.zip

https://www.un4seen....s/bassdsd24.zip

https://www.un4seen....s/bassenc24.zip

https://www.un4seen..../bassflac24.zip

https://www.un4seen..../bassmidi24.zip

https://www.un4seen..../bassopus24.zip

https://www.un4seen....asswasapi24.zip

https://www.un4seen....es/basswm24.zip

https://www.un4seen....es/basswv24.zip

https://www.un4seen..../bass_aac24.zip

[seeteeyou]

Anyway, I don't understand why these differences between G4D, BCD, and Ventoy, nor why the latter sounds so bad.

 

After going through quite a few Chinese / Russian / Turkish forums, even more alternatives were found.

 

 

 

First one is called "XORBOOT" from Pauly and he's also the developer of BOOTICE, I didn't realize what that was until I read something about "Multiboot Collection" as well as "MultiBoot Utility"

 

https://usbtor.ru/viewtopic.php?t=238

https://usbtor.ru/viewtopic.php?t=470

 

https://downloads.so... Utility En.exe

https://www.tnctr.co...lity-tr-en-v17/

 

Here's a link to version 0.65 for BIOS

 

https://web.archive....0764e290dd2c19f

https://web.archive....ic.php?f=3&t=66

https://www.softpedi...k/XORBOOT.shtml

https://reboot.pro/i...e=9#entry177404

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

https://www.tnctr.co...boot-multiboot/

 

0.80 for UEFI and 0.73 for BIOS, followed by XORBOOT UEFI 0.25

 

https://reboot.pro/i...=10#entry189476

https://www.mediafir...-12-27.rar/file

https://www.mediafir...-05-09.rar/file

https://soft.sibnet....-2019/download/

https://getsoft.sibn...u/get/?id=23297

 

 

 

Another one is called "AIO Boot NewGen" and it's based on GRUB 2

 

https://www.aioboot.com/en/download/

https://www.aioboot.com/en/newgen/

 

I assume that's a relatively easy way to give GRUB 2 a try without having to read the official documentation, at some point we might simply pick an example and then learn more about how to get GRUB 2 working manually.

 

And then we also have another version from a1ive a.k.a. wintoflash

 

https://a1ive.github...b2-filemanager/

https://github.com/a...ub2-filemanager

https://github.com/a1ive/grub

https://reboot.pro/i...showtopic=22429

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

 

Grub2Win is available here

 

https://sourceforge....grub2win/files/

 

Eventually we'll move on to the official version of GRUB 2 for Windows instead of relying on 3rd party software

 

https://ftp.gnu.org/...for-windows.zip

https://ftp.gnu.org/...for-windows.zip

https://ftp.gnu.org/...for-windows.zip

 

 

 

Boot WinPE EFI form GRUB2 CD/DVD

https://msfn.org/boa...rm-grub2-cddvd/

https://www.gnu.org/...stallation.html

https://www.gnu.org/...02dinstall.html

https://www.gnu.org/...CD_002dROM.html

https://www.gnu.org/...Device-map.html

https://www.gnu.org/...stallation.html

 

 

 

Booting BOOTMGR from syslinux/UBCD?

https://msfn.org/boa...m-syslinuxubcd/

 

UBCD 5.0 - Vista RE, Multiple WIMs, OS Install/Diagnostics

https://www.ultimate...opic.php?t=1931

 

RMPrepUSB - 62 - Chainload syslinux from grub4dos/grub/grub2 and vice versa

https://sites.google...inload-syslinux

 

Use syslinux to create an integrated USB flash drive for DOS, winpe, and slax Linux

https://topic.alibab...6_32332074.html

 

Many instructions for "SYSLINUX" should have mentioned the file ldntldr.bin and that's part of grubutils, it's also available from the author for G4D

 

https://github.com/c..._2015-02-15.zip

https://github.com/c...st/grubutils.7z

 

Previous versions of grubutils

 

https://code.google....utils/downloads

 

For some reasons "SYSLINUX" wasn't updated for several years already, the latest version of syslinux64.exe could be found inside syslinux-6.03.zip

 

https://mirrors.edge.../boot/syslinux/

 

Official documentation

 

https://wiki.syslinu...p?title=Install

https://wiki.syslinu...p?title=MEMDISK

https://wiki.syslinu...?title=SYSLINUX

 

FYI - here's an interesting example

 

https://www.twblogs....b7177781a0e9704

https://github.com/b..._Grub2_ISOLINUX

 

Similar stuff from beatfan

 

https://github.com/beatfan/BIOS_grub2

https://github.com/beatfan/UEFI_grub2

 

 

 

Finally we could actually add "wimboot" to G4D in order to boot off any *.wim files directly (stored on local drives) without having to create any *.iso images

 

https://github.com/i...releases/latest

https://www.cxyzjd.c...h2mm_1/80809644

https://blog.csdn.ne...etails/80809644

 

Other examples would support network booting as well

 

https://reboot.pro/t...sefii386x86-64/

http://mistyprojects...npe_wimboot.htm

https://ipxe.org/wimboot

[rdok]

Hi Samotec or anyone else,

 

Thank you for all the information in this thread. I found the courage to try for myself, though I am not that familiar with Windows,

I succesfully created  a bootable USB stick and a VHD, But after the Bootice BCD step I got lost.

In the pdf on the first post Samotec writes;
"Edit on the Boot\BCD the bootfile to:

\windows\system32\boot\winload.exe for MBR/CSM booting"

and a similar line for UEFI booting.

 

What is meant by that?
I tried editing the bcd file entering just the \windows... line

and

replacing the bcd fie by a link to \windows....

but both didn't work,

 

When restarting the PC I now get the choice between Windows10 and winPE but the latter won't start or starts the home Windows10 installation.

 

Help would be much appreciated!

rdok

[svet]

Hello, please some help. Following the manual of samotc, I imported registries twice via Windows PE Strelec in a USB
Pen that contains my Win11XPE. But on the last import, the Win11XPE at startup starts endless loading. I don't know how to restore the registries from before this import. I also have two Registry
Snapshots via RegistryChangesWiew.

[internethandle]

Can you provide more information? Were you trying to import in order to install drivers for your audio device//DAC? How far along are you in creation of PE? Does the same boot.wim that is not booting via USB stick (after putting back into a ISO with UltraISO) booting okay in VHD flatboot?

If you are early enough in the process of creating XPE, it may be easiest to just start over or otherwise just go back to your most recent VHD flatboot/create a new flatboot from the ISO you first created with the WinXPE program and try again.

It is always a good idea, in my experience with PE, to create a copy of the VHD I am working on (even if it is just before I transfer to USB boot) so that if I make a change I can just go back to the VHD (flatboot) that I know booted okay.