@spamtrash
Z tego co czytałem kiedyś na Wildersach, to telemetrię już wstawili
Z tego co czytałem kiedyś na Wildersach, to telemetrię już wstawili
@helium chyba tłumaczyłeś WFC , więc tutaj są nowe majtki do przetłumaczenia:
Czy ktoś dysponuje ostatnią wersją instalatora bez Malwarebytes? Mam na myśli 5.4.10 PL. Za udostępnienie będę wdzięczny
Zaloguj lub Zarejestruj się aby zobaczyć!
What's new in version 6.0.2.0 (04.03.2019)
- New: The notifications for svchost.exe include now the service name which generated
the blocked connection under the Name. Creating a rule for svchost.exe from the
notification dialog will always include the service in the newly created rule.
- New: Connections Log has now a new column for the Service name which is used by
svchost.exe. The lookup is made based on the ProcessID, therefore for older entries,
the exact service name can't be detected.
- Fixed: The width of some strings from Dashboard was extended to display properly
when a different language is used.
- Fixed: Rules properties are not updated in Rules Panel if they are open while
changing the user interface language.
- Fixed: Some group names are not displayed correctly in Rules Panel.
Changes in Windows Firewall Control 6.1.0.0 (2020-01-04):
- New: Added keyboard shortcuts for the Notification Dialog. For more information please refer to the ‘Keyboard shortcuts’ section from the user manual .
- New: Added ‘Select All’ context menu item for all text boxes.
- Fixed: Due to the latest SSL improvements on the hosting server, the check for a new version does not work anymore.
- Fixed: During install/update, after the UAC prompt, for 1-2 seconds is displayed the previous page instead of the progress page.
- Fixed: The uninstaller does not work if the WFC service can not be initialized.
- Fixed: In some rare cases, the uninstaller may hang during the uninstallation.
- Fixed: Sorting by Time Generated column in Connections Log does not work.
Zapewne dlatego:Czy działa wam wyszukiwanie aktualizacji w Windows (WU) przy włączonej zaporze (Średni profil filtrowania). Za cholerę nie mogę tego zrozumieć, dlaczego własny Firewall Windows blokuje własne aktualizacje. Interesuje mnie opinia użytkowników 8 i 10 bo podobno w siódemce ten problem nie występuje. Na niskim profilu filtrowania wszystko działa, ale przecież musi to działać także na średnim poziomie. Kombinowałem z różnymi ustawieniami ale niestety bez powodzenia, może ktoś ma jakieś doświadczenie w tym temacie
info z wildersów.As the developer of WFC, I already suggested the "WFC recommended rules" as a minimum set of rules that are required for normal Internet/LAN usage. They are covering a limited amount of svchost.exe, System and spoolsv.exe (printing support) outbound connections. Later, I also added some inbound rules for svchost.exe and System to this rules set, to be able to access a computer from another one from the same home network. Besides these rules for svchost.exe and System, I do not allow other connections of Microsoft Windows processes. dashost.exe, backgroundtransferhost.exe, systemsettings.exe, apphostregistrationverifier.exe, etc, all blocked. No problem since 2010. Now, decide for yourself if you want to allow them or not.
What's new in Windows Firewall Control 6.2.0.0
June 23, 2020
- Improved: Remote addresses content is now expanding to fill the available space in Properties dialog so that more content can be displayed
- Fixed: Properties dialog is not displayed anymore if two or more Windows services have the same Display Name
- Fixed: The service name for svchost.exe notifications is detected only for the Windows services that are already running when WFC service starts. If a Windows service is started after, the notification will not detect the Windows service that triggered the notification
- Fixed: Unhandled exception is logged if certain files are missing from the installation folder
- Fixed: When editing a rule details in the Notification dialog, the rule name can be set as one or several empty spaces
- Fixed: Properties dialog can't apply changes to a rule if the path of the rule is not accessible or not found. This limitation was removed. Also the tooltip was updated since a rule with red text does not always mean the file is not found, it can also mean the file is not accessible (file located in a folder of another user account encrypted location, etc)
- Fixed: In Notification dialog the text (Yes, No, Not valid) under Signed property is not localized
- Removed: The x button from text boxes that is clearing their content
Changes in 6.3.0.0:
- Improved: Detecting invalid rules is now made at service level instead of UI level, meaning that the rules defined for files that are not accesible are not detected anymore as invalid.
- Fixed: Connections Log loading time increased after last update if Security log contains older entries for processes that are not running anymore.