Thank you very much for answering, I forgot to mention that this problem happens to me in all builds, I tried in (1709, 1809, 20H2 and Windows 8.1) I currently tried in 8.1, I kept the component 'Diagnostics and Troubleshooting' and still did not detect the game, now I will try in 1709.It's the 'Diagnostics and Troubleshooting' component that is currently needed for CapFrameX game detection. Keep it until the next version, will see if possible to split the needed portion of it.
Sorry for the delay, and thank your buddy Matishzz over Twitter for bringing this to my attention.
It's true I am not supposed to be hunting dependencies all day as it's the expected nature of component removal, but I am interested when more people are influenced by it, same like there are compatibility options for Spotify, NVidia driver etc.
Keep me updated, I'll post here if a smaller component or a fix is in the next update.
Thanks.
Hi Nuhi, I just tried again in 1709, it worked, keep ''Diagnostics and Troubleshooting'' seems to have solved the problem, it seems that in Virtual Machine did not detect the game, so I had not been fixed, I currently tried in on my pc and works fine.It worked fine, attached my exact preset after loading yours, keeping Diagnostics and VMWare drivers (unimportant).
Maybe try it first, then we see why would it break with additions.
Once you confirm, I'll work on splitting Diagnostics for the exactly needed bits, as it's a big component and waste to keep it all.
Hi Nuhi, if it's worth I would like to comment that for me in 20H2 and 1909 CapFrameX works correctly without keeping "Diagnostics and Troubleshooting" and "Event Tracing for Windows".It worked fine, attached my exact preset after loading yours, keeping Diagnostics and VMWare drivers (unimportant).
Maybe try it first, then we see why would it break with additions.
Once you confirm, I'll work on splitting Diagnostics for the exactly needed bits, as it's a big component and waste to keep it all.
Great.Hi Nuhi, I just tried again in 1709, it worked, keep ''Diagnostics and Troubleshooting'' seems to have solved the problem, it seems that in Virtual Machine did not detect the game, so I had not been fixed, I currently tried in on my pc and works fine.
I will try different builds and let you know how it goes.
Interesting, then it could be older Windows only, probably MS split the needed functionality elsewhere later.Hi Nuhi, if it's worth I would like to comment that for me in 20H2 and 1909 CapFrameX works correctly without keeping "Diagnostics and Troubleshooting" and "Event Tracing for Windows".
Thanks for the info. OK then the compatibility option will have Diagnostics up to 1809, then from 1903 upwards no need.I just tested in 1809, keeping ''Diagnostics and Troubleshooting'' CapFrameX works perfectly as well as in 1709.
I just tried with 1803 and it doesn't work. I kept all EventLog and Diagnostics components.Alright, the others are:
- Event Log (as CapFrameX guys correctly hinted EWF, this is its core service)
- and .NET Framework 4 Presentation Foundation Core, as it seems to be a .NET application
When editing images, as opposed to deployed Windows (e.g. C:\Windows directly), enable OOBE compatibility as well - 1709 may need changes if going extreme (working on it).
Those OOBE components can be removed after setup.
And be careful about driver requirements, those are out of scope here, always enable Host Machine compatibility and/or VM of choice at least.
That's it as far as I see, let me know if anyone has a preset that breaks it, also make sure your tweaks and scripts are not doing it.
Bit fishy that it's just 1803 and those around it are fine, it's more likely that you did something different.I just tried with 1803 and it doesn't work. I kept all EventLog and Diagnostics components.
First I tried on VMWare but it doesn't work (Even installing VMWare Tools). Then I tried it on my PC but it doesn't work either.
The only different thing is that I disabled the services that the diagnostics component adds. However on 1709 and 1809 it worked without problems even disabling the services.
I just tested leaving the necessary components and default services, it still doesn't work. I tested it in virtual machine installing "VMware Tools".Bit fishy that it's just 1803 and those around it are fine, it's more likely that you did something different.
Anyway, logically do not disable those services if they are needed, and let me know when you confirm.
I might put a lock on those services when the compatibility is enabled.
If you see a problem with just removals and no manual tweaking, including service disabling, let me know.
These 3 are a must keep when testing this:
Diagnostics
Event Log
.NET Framework 4 Presentation Foundation Core
Well, then please attach that exact preset, and make sure it is true without any extra tweaks which I would not see when testing.I just tested leaving the necessary components and default services, it still doesn't work. I tested it in virtual machine installing "VMware Tools".
I tried several times in virtual machine and something very strange just happened; at first it detected the game and everything worked correctly, then I restarted the virtual machine; I did everything exactly the same but this time it did not detect the game. Other times that I used the same preset it never detected the game, now it detected it once but it only worked until I restarted the virtual machine.Well, then please attach that exact preset, and make sure it is true without any extra tweaks which I would not see when testing.
Thanks.
The preset does not add any scripts or registry changes. It only removes components, it does not disable services.Thanks, will let you know when I try in a day or so.
Noted the extra reboot requirement.
You also make sure that something wasn't applied after setup via your setupcomplete or whatever and it disabled the necessary service, as it sounds like that is happening if first reboot it works.
Just mentioning it in case it's something obvious, of course if only the core tool was used when testing this, then allow me to report back.