Windows Firewall Control (WFC) by BiniSoft.org

After resetting WFC I have the same problem.

I received the following messages:

Informationen über das Aufrufen von JIT-Debuggen
anstelle dieses Dialogfelds finden Sie am Ende dieser Meldung.

************** Ausnahmetext **************
System.NullReferenceException: Der Objektverweis wurde nicht auf eine Objektinstanz festgelegt.
bei WindowsFirewallControl.Common.ViewManager.OpenProperties(RuleData ruleData, ViewPurpose viewPurpose)
bei WindowsFirewallControl.Common.ViewManager.OpenRulesPanel()
bei System.Windows.Forms.ToolStripItem.RaiseEvent(Object key, EventArgs e)
bei System.Windows.Forms.ToolStripMenuItem.OnClick(EventArgs e)
bei System.Windows.Forms.ToolStripItem.HandleClick(EventArgs e)
bei System.Windows.Forms.ToolStripItem.HandleMouseUp(MouseEventArgs e)
bei System.Windows.Forms.ToolStrip.OnMouseUp(MouseEventArgs mea)
bei System.Windows.Forms.ToolStripDropDown.OnMouseUp(MouseEventArgs mea)
bei System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
bei System.Windows.Forms.Control.WndProc(Message& m)
bei System.Windows.Forms.ToolStrip.WndProc(Message& m)
bei System.Windows.Forms.ToolStripDropDown.WndProc(Message& m)
bei System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Geladene Assemblys **************
mscorlib
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4180.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll.
----------------------------------------
wfc
Assembly-Version: 6.1.0.0.
Win32-Version: 6.1.0.0.
CodeBase: file:///C:/Program%20Files/Malwarebytes/Windows%20Firewall%20Control/wfc.exe.
----------------------------------------
PresentationFramework
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4180.0.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.dll.
----------------------------------------
WindowsBase
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4180.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/WindowsBase/v4.0_4.0.0.0__31bf3856ad364e35/WindowsBase.dll.
----------------------------------------
System.Core
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4180.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll.
----------------------------------------
System
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll.
----------------------------------------
PresentationCore
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4180.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_64/PresentationCore/v4.0_4.0.0.0__31bf3856ad364e35/PresentationCore.dll.
----------------------------------------
System.Xaml
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4180.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xaml/v4.0_4.0.0.0__b77a5c561934e089/System.Xaml.dll.
----------------------------------------
System.Configuration
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll.
----------------------------------------
System.Xml
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll.
----------------------------------------
System.ServiceProcess
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ServiceProcess/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.ServiceProcess.dll.
----------------------------------------
mscorlib.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/mscorlib.resources/v4.0_4.0.0.0_de_b77a5c561934e089/mscorlib.resources.dll.
----------------------------------------
System.Runtime.Remoting
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll.
----------------------------------------
System.Windows.Forms
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll.
----------------------------------------
System.Drawing
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll.
----------------------------------------
System.ServiceModel
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4180.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel/v4.0_4.0.0.0__b77a5c561934e089/System.ServiceModel.dll.
----------------------------------------
System.Runtime.Serialization
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4180.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Serialization.dll.
----------------------------------------
SMDiagnostics
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4180.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/SMDiagnostics/v4.0_4.0.0.0__b77a5c561934e089/SMDiagnostics.dll.
----------------------------------------
System.ServiceModel.Internals
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4180.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.ServiceModel.Internals/v4.0_4.0.0.0__31bf3856ad364e35/System.ServiceModel.Internals.dll.
----------------------------------------
System.IdentityModel
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4180.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.IdentityModel/v4.0_4.0.0.0__b77a5c561934e089/System.IdentityModel.dll.
----------------------------------------
System.RunTime.Serialization.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Serialization.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Runtime.Serialization.resources.dll.
----------------------------------------
PresentationFramework.Aero2
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework.Aero2/v4.0_4.0.0.0__31bf3856ad364e35/PresentationFramework.Aero2.dll.
----------------------------------------
PresentationFramework.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework.resources/v4.0_4.0.0.0_de_31bf3856ad364e35/PresentationFramework.resources.dll.
----------------------------------------
PresentationCore.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationCore.resources/v4.0_4.0.0.0_de_31bf3856ad364e35/PresentationCore.resources.dll.
----------------------------------------
PresentationFramework-SystemXml
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework-SystemXml/v4.0_4.0.0.0__b77a5c561934e089/PresentationFramework-SystemXml.dll.
----------------------------------------
UIAutomationTypes
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4180.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/UIAutomationTypes/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationTypes.dll.
----------------------------------------
UIAutomationProvider
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4180.0 built by: NET48REL1LAST_B.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/UIAutomationProvider/v4.0_4.0.0.0__31bf3856ad364e35/UIAutomationProvider.dll.
----------------------------------------
PresentationFramework-SystemCore
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/PresentationFramework-SystemCore/v4.0_4.0.0.0__b77a5c561934e089/PresentationFramework-SystemCore.dll.
----------------------------------------
System.Windows.Forms.resources
Assembly-Version: 4.0.0.0.
Win32-Version: 4.8.4084.0 built by: NET48REL1.
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms.resources/v4.0_4.0.0.0_de_b77a5c561934e089/System.Windows.Forms.resources.dll.
----------------------------------------

************** JIT-Debuggen **************
Um das JIT-Debuggen (Just-In-Time) zu aktivieren, muss in der
Konfigurationsdatei der Anwendung oder des Computers
(machine.config) der jitDebugging-Wert im Abschnitt system.windows.forms festgelegt werden.
Die Anwendung muss mit aktiviertem Debuggen kompiliert werden.

Zum Beispiel:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

Wenn das JIT-Debuggen aktiviert ist, werden alle nicht behandelten
Ausnahmen an den JIT-Debugger gesendet, der auf dem
Computer registriert ist, und nicht in diesem Dialogfeld behandelt.

 

I just checked for Windows Updates and it installed on my side the same version as yours. The Properties dialog works as before on my laptop. However, it installed some unwanted drivers and some unwanted Windows Store apps. This Windows 10 is more and more intrusive and annoying.



LATER EDIT: I did the same upgrade on a virtual machine and it works after the major update. I was hoping that I might be able to reproduce it on a non development machine.

 

Thank you for trying and fast answering!

Difficult situation now ... perhaps it could be related to non-us Win Versions (because I have a swiss german edition here)??

I hope you can use the error messages in my pre-last posting somehow or you can something "shoot in the wild" to make a fix ...

I am pretty sure, there are more users too with this problem. Of course I understand, that it's very difficult if you can't reproduce it!

I just hope for a solution!

PS: I even resetted the rules too, no change. I tried also for testing to run the GUI with admin rights, also no change ... and last but not least I ran the .MS NET repair tool which doesen't found any problems. At the moment, I am out of idea ...

PPS: One idea yet, could it be related to WPF?
https://github.com/dotnet/wpf/issues/2357
https://stackoverflow.com/questions/1472498/wpf-global-exception-handler
https://docs.microsoft.com/en-us/do...handledexceptioneventhandler?view=netcore-3.1

And I had (for 1909 yet) installed the following .NET update:
December 10, 2019-KB4533002 Cumulative Update for .NET Framework 3.5 and 4.8 for Windows 10 Version 1903 and Windows Server 1903 RTM and Windows 10, version 1909 and Windows Server, version 1909

Also perhaps more .NET updates before Win 10 May Update, for ex. for .NET 4.5 ...

Who knows if this could be related?

(Edited: added the result from MS .NET repair tool, added the hint for cumulative .NET update)
(Later edited: more hints about possible .NET updates)

 

You need feedback from users with the same or German OS interface language. For example, Macrium Reflect twice corrected an error that occurs only on German OS.

 

Let me download and install version 1909 German edition and let Windows Update do its thing and lets see. I will come back later with my findings.


LATER EDIT: I installed build 18363.418, it installed some updates until it got to build 18363.836 and now it does not get any new updates.

 

LATER LATER EDIT:
I forced it to update by using the Windows 10 Assistant. It works with a non English version of Windows 10.



I don't know what is going on.

 

It works for you on German Windows, there are no complaints from other users of German Windows, which means that alpengreis has a local problem on its OS.

 

Others reported the same problem on English version too but it does not happen on my side. Without being able to reproduce it, I can't provide a fix.

 

BTW: I have NOT a german Win edition, I have a SWISS german Win edition, that's not the same (german = de_CH, swiss german = de_CH). For example swiss german edition has other decimal sign (german = ",", swiss german = "."). Or german has the ß, we not. Also german has another location for Store and they have support for Cortana (we not). Aaaaand, they have other keyboard layouts with other language packs, other auto-correction ...

 

Yes, that's sometimes very "weird". BTW: I have a SWISS german edition, see details above ...

 

@alexandrud

Perhaps something like the following (example only) could help? ...

Code:

 namespace UnhandledExceptions
{
    public partial class MainWindow : Window
    {
        List<String> l = null;

        public MainWindow()
        {
            InitializeComponent();
            Application.Current.DispatcherUnhandledException += Current_DispatcherUnhandledException;
        }

        private void Current_DispatcherUnhandledException(object sender, System.Windows.Threading.DispatcherUnhandledExceptionEventArgs e)
        {
            MessageBox.Show(e.Exception.ToString());
            Application.Current.Shutdown();
            e.Handled = true;
        }

        private void Button_Click(object sender, RoutedEventArgs e)
        {
            l.Add("A");
        }
    }
}

Resp ...

App.XAML:

Code:

DispatcherUnhandledException="Application_DispatcherUnhandledException"

App.cs:

Code:

private void Application_DispatcherUnhandledException(object sender, System.Windows.Threading.DispatcherUnhandledExceptionEventArgs e)
   {

       e.Handled = true;
   }

 

I am on Swiss German Win 10 edition here, build 19041.264.
WFC seems to be working normally, apart from the notifications. Since the Win 10 2004 upgrade, I only get these using an account with admin rights, not as standard user. A reinstall of WFC fixed it until (probably) the next restart, then no notifications again.

 

@almasy

Thanks for reporting! At least we know now that it's not related to a certain Windows version. Weird, well - of course - the same platform is also not a guarantee that it runs then correctly. It seems deeper (within the .NET or something like this (at least .NET seems okay here, maybe its config or so?)) ... could also be that other software has an influence somehow (perhaps security software), etc etc ...

PS: I tried a complete CLEAN reinstall of WFC (deleted all stuff before, including the related registry keys), no success.

 

Hi,
can a firewall rule block the complete internet access for a certain user while another user has full access?
Example: User 1 is online. This is followed by a change to User 2 (User 1 remains logged in, will not be logged out in Windows!)
Now user 2 should be blocked from accessing the Internet for all programs without restricting user 1.
thx for great program!

 

100% a clean reinstall of the operating system would solve this. I think there is a combination between preinstalled software + installed .NET Framework updates which breaks the functionality. I still can't reproduce it.

What happens when you click on Blank rule ?

 

It is possible, but not from WFC user interface. You have to edit the properties of the existing firewall rule in WFwAS. Define an outbound block rule that applies to all programs, all ports, all everything. Open it and add yourself in the Exceptions list so that it won't apply to your user. For other users, it will block the connections. At least, this is how it should work, I never tried.

 

thx alexandrud,
I have already tested this (block all outgoing connections) and unfortunately it does not work properly. Firefox and Edgebrowser continue to get through etc.
I cannot rule out every single program.

Could it be important where the firewall rule is? So at the top, in the first place e.g.? If so, how can you determine that?

 

Create two batch .bat files and create two scheduler tasks for specific users that will execute the first or second rule.

Netsh.exe Advfirewall Firewall add rule name="High Filtering profile - Block outbound connections" dir=out action=block description="Block all outbound connections"
Netsh.exe Advfirewall Firewall add rule name="High Filtering profile - Block inbound connections" dir=in action=block description="Block all inbound connections"
Netsh.exe Advfirewall Firewall delete rule name="High Filtering profile - Block all outbound connections"
Netsh.exe Advfirewall Firewall delete rule name="High Filtering profile - Block all inbound connections"
Or similarly, when changing the user, with batch files turn Off or turn On the network card.
Or import the complete set of rules #1 or #2.
Or use Windows Parental Control.
Or use third-party software.

 

In Windows Firewall, the order of the rules (higher, lower) does not matter. In addition, the new rule is always on the first line.

 

KB4552931 – Information

This is classified as a cumulative update to .NET framework for Windows 10 and it asks for a restart.

Following that restart, my WFC try icon displayed a shriek (!) suggesting that its service was not running. A further restart did not change anything. I was able to restart the service manually, the ! returned to √ as one would expect and thereafter, things appeared to return to normal.

 

Blank rule also fails.

For the moment I use WFC without the possibility to edit rules (I make this in "old" original GUI) ...

I have no other preinstalled software than I always had (I think). Unfortunately I can't make a clean install of Win on this machine (maybe in few monts, but not now) ...

However: thank you for your effort, Alexandru, I apprieciate that ... who knows, at some point we will have a solution hopefully ... (I will be stay tuned too, try some things etc.).

 

@Plutox @alexandrud

Interesting point, thank you, Plutox! You had also the problem with the rules edit (no rule properties)?

Alexandru, also this cumulative .NET update was installed here too on my 1909 machine yet, If I remember correctly ...

 

Is there anyway to prevent windows firewall or eventviewer from logging a specific application's internet activity?

 

No. It is all or nothing.

 

@alexandrud
WFC cannot merged the rules created for "All Programs" (empty Program column in the Rules Panel). That is unnecessary? (A workaround exists).
And we waiting for new version