Open gepardec-wf opened 1 year ago
also, there is still no simple solution to make windows update work, when blocking svchost and allowing only certain services.
As you have already mentioned, this is unfortunately a general unsolved problem in Windows 10 and not WFN specific.
The only "solution" is AFAIK to copy svchost.exe and use the new path/filename in the service executable path.
Hi there, sorry I also missed this issue. 2.5 beta had some issues I fixed in the nightlies - I know I should release a version 2.6 asap since it has a lot of improvements but I still had to fix some things first... To be continued.... ;-)
Hi Wokhan!
The following happened on virgin Windows 11 installations with the Standalone 64 bit version of version 2.5 beta on two different systems. in this order:
see images attached below.
probably unrelated:
after quitting the application and playing around a little, i found a manual fix:
another unrelated minor "bug": The application title says Amd64, even tough I have an intel CPU. just seems to be cosmetics and wrong wording, but affects the user experience too ;-)
greetings!
Long time user of this great software.
BTW: Thanks for cleaning up the releases page and introducing the better notifier background task to fix the millions of notifier instances. Happy to see there are some new changes on the way. I personally would prefer a minimal version for download with just the main notifier functionality and the configuration of it. maybe you could reintroduce the version without the database to keep the wfn footprint to a minimum. also, there is still no simple solution to make windows update work, when blocking svchost and allowing only certain services. that would be the last killer feature missing, but i suspect that is the fault of its questionable implementation. some other software seemed to have found some kind of fix for that, but to me it looks more like a hack and I would rather not prefer to do it that way (https://github.com/henrypp/simplewall/issues/677).