[SOLVED] [EX-100 v2.3.6.0][20H1 Build 19041.264] Some troubles when Removing components.

Hello, winterstorm

I had some trouble reducing 20H1. (No problem until 19H2)

If Modern UI Apps - Framework (Visual C++ Runtime) is Removed,
CPU usage is very high.
(Almost one core of CPU is occupied by AppX Deployment Service (AppXSVC).)

   


If Windows Error Reporting Service is Removed,
a taskbar stops responding or a start menu cannot be opened.

   

If it is Auto/Manual or Diable, there seems to be no problem.

Hi Lucyrier
Modern UI Apps - Framework (Visual C++ Runtime)   should never be removed
as it is needed for a lot of programs
In my opinion  Winterstorm should remove this option, together with  Framework (.NET Native) 
From Winreducer, but who am I ??


icy

Hello guys

@Lucyrier : Very interesting report, thank you very much for the details, there is another report about the 20H1 start menu issue :
[You must be registered and logged in to see this link.]
I found that the start menu is working accordingly of all previous version (but it still works on my computer, I only have a lag to open it) ... I will try with your discoveries.

@icy007 : thanks for the idea ... but the purpose of WinReducer Series software is to remove as much as possible Windows components (sometimes it breaks more things than expected and sometimes not related) ... and "Modern UI Apps - Framework (Visual C++ Runtime)" is one of them, at least until it will not hang the system ... so I will let the choice to all users to delete all components, especially for all people who do not want to use Modern UI Apps ... and to be honest I'm one of them ... I only keep "Settings" apps (which by the way, does not required a single Modern UI Apps Frameworks) ... and just between you and me, WinReducerOS will be there to propose an entire and global alternative in terms of UX and UI for Windows 10

And you want something funny .... Windows 10 have, at the moment, 9 active different versions (with LTSB and LTSC included) to support, with their respective cumulative updates ! I'm not a MS engineer, so if you have an idea about : "why this is like this", I'm really interesting ... the only explanation I have is : "why doing simple when you can do complicated" !

Hi icy007,

I'd try not to remove Framework (Visual C++ Runtime) for a while.

I'm interested to see if it works even if I remove Runtime as before 19H2.
I would like winterstorm to investigate first,
If there is no effective workaround, After 20H1, it is safer to remove this option as you mentioned.

@winterstorm: I haven't read every topic in every corner,
so I'm sorry to build one independently.
I will also read that topic. Thank you for your investigation.

@Lucyrier : no problems my friend, this was just for reference and a potential resource for a future test

EDIT : I will investigate because it seems to be confirmed

I was able to verify it in build 19042.631. Thanks for the great improvement!