Hi,
unfortunately cannot replicate, here are some findings which may clue us in:
- I'm using VMWare instead of VirtualBox, driver protection kept
<c>driver_c_memory.inf</c>
<c>driver_lsi_sas.inf</c>
<c>driver_memory.inf</c>
I would keep Memory related components regardless of the machine.
Also make sure to install Guest VM tools/drivers before continuing after setup, if wasn't already.
- Since it's just 10 components, should be easy to retest using snapshotting in a VM and let me know exactly which component is it
I suggest it might be one of these:
<c>appreadiness 'App Readiness'</c> (maybe it needs time after install to propagate some app readiness, start menu is also an app)
<c>clipsvc 'Client License Service (ClipSVC)'</c> (related to Windows activation, similar to above, or maybe not even removable)
<c>tempcache 'Cache and temp files'</c> (it might delete something temporary that the machine is currently working on)
But of course if not, try the others.
- Try VMWare Player/Workstation as the last resort, as we might be hunting a VirtualBox bug/driver dependency.
It's just these 10 removals do not ring anything special to it, if it was drivers, maybe.
If by a slim chance you confirm that it works with VMWare, then I'll setup a VirtualBox setup and give it another try.
Thanks.