Windows Editions Reconstruction Project

windows audio is broke. it has happened before. everytime I switch to rdsh and switch back. windows audio does not work. devices show up in device manager, the service is running. programs do not think any audio device is installed

When you switch to rdsh. it wants to install feature when you reboot

I got audio back. I switched to rdsh, let it do its thing, then switched back to workstation, now audio is back

 

as I stated:
But it may ask for server driver for few devices, like network adapter.

 

I got audio back

 

Yes. Good.

Basic tools and skills are important.

Skills can be obtained from scripts.

 

ok

 

Good night.

 

You need to login to view this posts content.

 

you can use the core certificates to change wndows editions back to home. when you change back to home, features turned on when going to pro are turned off. no reboot need. it is like going from pro to enterprise. With the Starter certificates, you might be able to switch the edition to starter.

 

Thank's, But it's not that simple, if only it was, there would be no need for Windows Editions Reconstruction Project.

 

[vNext ServerDatacenter Desktop Experience]

Code:

Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~10.0.20257.1000.esd

Microsoft-Windows-ServerCore-Package~31bf3856ad364e35~amd64~~10.0.20257.1000.esd

Microsoft-Windows-EditionSpecific-ServerDatacenter-Package~31bf3856ad364e35~amd64~xx-XX~10.0.20257.1000.esd
Microsoft-Windows-EditionSpecific-ServerDatacenter-Package~31bf3856ad364e35~amd64~~10.0.20257.1000.esd

Microsoft-Windows-EditionPack-Server-Package~31bf3856ad364e35~amd64~xx-XX~10.0.20257.1000.esd
Microsoft-Windows-EditionPack-Server-Package~31bf3856ad364e35~amd64~~10.0.20257.1000.esd
Microsoft-Windows-EditionPack-Server-WOW64-Package~31bf3856ad364e35~amd64~xx-XX~10.0.20257.1000.esd
Microsoft-Windows-EditionPack-Server-WOW64-Package~31bf3856ad364e35~amd64~~10.0.20257.1000.esd

Microsoft-Windows-Server-DesktopUX-Package~31bf3856ad364e35~amd64~xx-XX~10.0.20257.1000.esd
Microsoft-Windows-Server-DesktopUX-Package~31bf3856ad364e35~amd64~~10.0.20257.1000.esd
Microsoft-Windows-Server-DesktopUX-WOW64-Package~31bf3856ad364e35~amd64~xx-XX~10.0.20257.1000.esd
Microsoft-Windows-Server-DesktopUX-WOW64-Package~31bf3856ad364e35~amd64~~10.0.20257.1000.esd

Microsoft-Windows-EditionPack-Server-Full-Package~31bf3856ad364e35~amd64~xx-XX~10.0.20257.1000.esd
Microsoft-Windows-EditionPack-Server-Full-Package~31bf3856ad364e35~amd64~~10.0.20257.1000.esd
Microsoft-Windows-EditionPack-Server-Full-WOW64-Package~31bf3856ad364e35~amd64~xx-XX~10.0.20257.1000.esd
Microsoft-Windows-EditionPack-Server-Full-WOW64-Package~31bf3856ad364e35~amd64~~10.0.20257.1000.esd

Microsoft-Windows-EditionPack-Server-Roles-Full-Package~31bf3856ad364e35~amd64~xx-XX~10.0.20257.1000.esd
Microsoft-Windows-EditionPack-Server-Roles-Full-Package~31bf3856ad364e35~amd64~~10.0.20257.1000.esd

Code:

Microsoft-Windows-EditionPack-ServerDatacenter-Package~31bf3856ad364e35~amd64~xx-XX~10.0.20257.1000.esd
Microsoft-Windows-EditionPack-ServerDatacenter-Package~31bf3856ad364e35~amd64~~10.0.20257.1000.esd

Microsoft-Windows-EditionPack-ServerDatacenter-Except-ACor-Package~31bf3856ad364e35~amd64~xx-XX~10.0.20257.1000.esd
Microsoft-Windows-EditionPack-ServerDatacenter-Except-ACor-Package~31bf3856ad364e35~amd64~~10.0.20257.1000.esd

 

Q: How does Windows create install.wim?

 

I believe I missed a lot of wonderful replies during my sleep.

Where does the StarterEdition come from？
Maybe they are just compiled from source code.

What determines the version to which the StarterEdition can be upgraded？
The early leaked builds of Windows suggested that the ServerEdition were upgraded from the ClientEdition.
Maybe some files and registries determine them.

Maybe StarterEdition can be upgraded to any editions if conditions permit.

 

15063.0. (Last reply)

 

There's just one setupapi, with recovery/reset/mediacreationtool(setuphost) etc all plugging into it

C:\Windows\servicing\Editions stuff is the public facing for Component-Based Servicing, TrustedInstaller does extra private stuff.
There are also other UpdateHandlers available AppX, Driver, Product etc.
for example I prevent feature updates alone in my private windows_update_toggle just by manipulating update handlers,
so WU does not return them and unlike other blockers, retain full WU functionality (for defender cloud, store, drivers etc).

But that's the old way.
Microsoft have migrated the most interesting stuff to "Feature Experience" that is managed via WNF.
The beauty/evil of WNF is that it is always listening passively,
so Microsoft can remotely toggle features just for some region, country, language, device or configuration.
Lately they've been playing a lot with this, way too many experiments in 20H2 for my liking hence why I'm staying on 2004 or older for as long as I can.

 

microsoft account says my version of windows 10 enterprise ltsc is 2009. not 1809

 

dorfd1 dism /online /get-targeteditions does not show enterpriseS

 

the microsoft account web page, shows the edition you are using

 

Q: Possible to create 20257.1000 Server with 20257.1 Professional?
A: Impossible. Mismatched SS build.

 

Q: Why ServerDatacenterCor failed too.
A: The package capture is incomplete.

 

Did you say that you can test ARM64? QEMU or physical devices?