Which missing Components cause those issues on Windows 11?

Od1sseas

New Member
Messages
29
Reaction score
4
Hello!
I used the "Lite" template with all Apps+Modern app support+Bluetooth+VPN+OOBE+Activation+Fonts+WLAN+Host Machine+VirtualBox compatibility and i have some issues with a few apps.

1) The MSI Afterburner setup doesn't work. After i click install it just closes after a few seconds and generates this log file.
View attachment 12885

2) Firefox setup gives an error just when it's about to finish installing.
View attachment 12886

3) Some context menu items don't work. When i click on them they don't do anything. TakeOwnershipPro is one of the affected apps.
View attachment 12887

Does anyone know which missing componenets cause those issues? Thanks.
 
Please attach your preset, after removing any user passwords or license keys.
 
Removing Client.CBS (Windows Feature Experience Pack - Desktop) will break your desktop.

At this point in time, I don't trust 24H2 is stable yet. Wait until next month's update (which should be around the RTM date), and try again with a newer image. Until then, it's throwing all sorts of random "referenced memory" errors.

Two more components you should not remove:
Code:
                <c>eventtracing 'Event Tracing for Windows (ETW)'</c>
                <c>winsxs 'Windows Component Store (WinSxS)'</c>
 
Removing Client.CBS (Windows Feature Experience Pack - Desktop) will break your desktop.

At this point in time, I don't trust 24H2 is stable yet. Wait until next month's update (which should be around the RTM date), and try again with a newer image. Until then, it's throwing all sorts of random "referenced memory" errors.

Two more components you should not remove:
Code:
                <c>eventtracing 'Event Tracing for Windows (ETW)'</c>
                <c>winsxs 'Windows Component Store (WinSxS)'</c>
Ok. I will try the same but without removing CBS, ETW and WinSxS.
Thanks.
 
Removing Client.CBS (Windows Feature Experience Pack - Desktop) will break your desktop.

At this point in time, I don't trust 24H2 is stable yet. Wait until next month's update (which should be around the RTM date), and try again with a newer image. Until then, it's throwing all sorts of random "referenced memory" errors.

Two more components you should not remove:
Code:
                <c>eventtracing 'Event Tracing for Windows (ETW)'</c>
                <c>winsxs 'Windows Component Store (WinSxS)'</c>
Only the context menu issue got fixed (It was because of CBS). I still have the same issues with Firefox Setup and MSI AF Setup.
Stock 24H2 does not have those problems so its definitely a missing component.
 
An old thread suggests restoring Error Reporting. It won't fix why the installer fails, but it make the error handler not throw out an uninformative error message.
Code:
                <c>errorreporting 'Windows Error Reporting'</c>
 
An old thread suggests restoring Error Reporting. It won't fix why the installer fails, but it make the error handler not throw out an uninformative error message.
Code:
                <c>errorreporting 'Windows Error Reporting'</c>
Ok I will try it thanks!
BTW I found the solution of the MSI AF installer. It was PowerShell 32 bit that was needed.
Now only the Firefox installer is left.
 
Last edited:
An old thread suggests restoring Error Reporting. It won't fix why the installer fails, but it make the error handler not throw out an uninformative error message.
Code:
                <c>errorreporting 'Windows Error Reporting'</c>
Error reporting didn't give me any clue but i made some progress myself and the results are really weird.
- Removing just the components (Lite template), the Firefox installer works perfectly fine.
- Removing just the optional features, the Firefox installer works perfectly fine.
- Removing both (Components + Optional Features) will break the Firefox installer.

I have no clue why this happens. Help?
 
Back
Top