every time i open the patchmypc i started to get this past one month
attached the picture/photo of the error i get
when i click 'details'errorofpatchmypc.jpg :
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Management.ManagementException: Invalid class
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
at System.Management.ManagementObjectCollection.get_Count()
at Microsoft.VisualBasic.Devices.ComputerInfo.get_OSManagementBaseObject()
at Microsoft.VisualBasic.Devices.ComputerInfo.get_OSFullName()
at PatchMyPC.PMPC.patch_Load(Object sender, EventArgs e)
at System.EventHandler.Invoke(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9139.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/mscorlib.dll
----------------------------------------
PatchMyPC
Assembly Version: 4.5.0.3
Win32 Version: 4.5.0.3
CodeBase: file:///C:/Users/lawre/Desktop/PatchMyPC.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 14.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9139.0 built by: NET481REL1LAST_B
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9151.0 built by: NET481REL1LAST_C
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9093.0 built by: NET481REL1LAST_C
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.9037.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9037.0 built by: NET481REL1
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.9037.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------
System.Management
Assembly Version: 4.0.0.0
Win32 Version: 4.8.9037.0 built by: NET481REL1
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/System.Management/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Management.dll
----------------------------------------
Microsoft.Win32.TaskScheduler
Assembly Version: 2.5.28.0
Win32 Version: 2.5.28.0
CodeBase: file:///C:/WINDOWS/Microsoft.Net/assembly/GAC_MSIL/Microsoft.Win32.TaskScheduler/v4.0_2.5.28.0__0d013ddd5178a2ae/Microsoft.Win32.TaskScheduler.dll
----------------------------------------
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Could you try to repair Microsoft .NET framework and see if that helps?
same here. I already tried to uncheck and check the default .net framework packages from "install features", I already run "sfc /scannow" and also I tried to repair the .net framework 7, but nothing changed.
I have the following .net framework packages installed:
(https://i.imgur.com/5UEghds.png)
(https://i.imgur.com/GK5y94Q.png)
Quote from: g3nsvrv on July 25, 2023, 07:40:34 PMsame here. I already tried to uncheck and check the default .net framework packages from "install features", I already run "sfc /scannow" and also I tried to repair the .net framework 7, but nothing changed.
I have the following .net framework packages installed:
(https://i.imgur.com/5UEghds.png)
(https://i.imgur.com/GK5y94Q.png)
Have you tried uninstalling and reinstalling the publisher on there?
I have the same problem after upgrading to Windows 11. Under Windows 10, PatchMyPC worked fine. I have .NET Framework installed, just like the other users in this thread. I would *highly* appreciate a fix for this problem.
Regards, Jaap.
Hi Jaap, what release of PMPC are you using? The latest is 4.5.0.4 and works fine on Windows 11.
Hello David, thanks for replying. It's 4.5.0.4, but still, I get the error numerous users here have mentioned from Microsoft .NET Framework.
Can you try to repair your .Net Framework installation using this article: Microsoft .NET Framework Repair Tool (https://support.microsoft.com/en-us/topic/microsoft-net-framework-repair-tool-is-available-942a01e3-5b8b-7abb-c166-c34a2f4b612a)
Quote from: Pete on July 26, 2023, 12:32:29 AMHave you tried uninstalling and reinstalling the publisher on there?
What do you mean by "the publisher"?
Our product PMPC is commonly referenced as "publisher "
Quote from: Justin Chalfant (Patch My PC) on September 26, 2023, 09:32:03 AMOur product PMPC is commonly referenced as "publisher "
ª
I'm using the portable version. It auto update itself regularly.
You are using the Home Updater, which is the free version. It is a portable app and runs seamlessly, if you are having issues then it is caused by your OS upgrade. You will need to repair your .Net Framework installation using this article: https://support.microsoft.com/en-us/topic/microsoft-net-framework-repair-tool-is-available-942a01e3-5b8b-7abb-c166-c34a2f4b612a
Quote from: Wes Mitchell on September 26, 2023, 12:42:26 PMYou are using the Home Updater, which is the free version. It is a portable app and runs seamlessly, if you are having issues then it is caused by your OS upgrade. You will need to repair your .Net Framework installation using this article: https://support.microsoft.com/en-us/topic/microsoft-net-framework-repair-tool-is-available-942a01e3-5b8b-7abb-c166-c34a2f4b612a
Hi, I already ran that but didn't work
Hello,
Thanks for reaching out on the forum! For those still affected by this, have you tried to redownload the latest version of the PMPC Publisher to see if that resolves any issues? Have you also tried running the portable version from another windows 11 device and do you see the same error?
Can you also try to run the DISM command to repair any corrupt files:
DISM /Online /Cleanup-Image /RestoreHealth
Quote from: Spencer (Patch My PC) on September 26, 2023, 12:58:09 PMHello,
Thanks for reaching out on the forum! For those still affected by this, have you tried to redownload the latest version of the PMPC Publisher to see if that resolves any issues? Have you also tried running the portable version from another windows 11 device and do you see the same error?
Can you also try to run the DISM command to repair any corrupt files:
DISM /Online /Cleanup-Image /RestoreHealth
I also ran dism and sfc
Can you attempt to manually install the latest .NET Framework ver. manually (online or offline installer) and see if it allows you to do so. The error shown is typical with .NET being corrupted in some way.
https://dotnet.microsoft.com/en-us/download/dotnet-framework/net481
Thanks to everyone who took the time and trouble to make a suggestion! I've tried to follow them. Which means:
- I've removed .Net Framework via "Turn Windows features on or off";
- I've downloaded and installed the most recent version of .Net Framework Runtime (4.8.1);
- I've removed PatchMyPC.exe from its location om my hard disk and re-copied it (same version, 4.5.0.4) from the Downloads directory to its previous location.
The result of all this is that the error window from .NET Framework now only pops up if I use the switch "/auto" with PatchMyPC. The error message is: "File format is not valid". If I click the "Continue" button in the error window, PatchMyPC does what it should do and exits. If I use PatchMyPC without switches, there is now no error anymore and it remains open. I can live with that, although I like that /auto switch.
I'm using the free version of PatchMyPC, which is why I wasn't familiar with the term "Publisher".
Regards, Jaap.
I forgot to mention that I also used the .NET repair tool after installing the latest .NET runtime. However, that made no difference.
Is there any chance of repairing the problem with the /auto switch?
What is the output of Get-Package -Name "Microsoft .Net*" | Select-Object -Property Name
You might try doing a repair of Windows 11 using an In-Place Upgrade.
Do a full drive image backup first, in case there is no change.
Worst case is you roll back to where you are now.
Hello OldNavyGuy,
thanks for replying. The output is:
Name
----
Microsoft .NET Host - 6.0.14 (x64)
Microsoft .NET Host FX Resolver - 6.0.14 (x64)
Microsoft .NET Runtime - 6.0.14 (x64)
Microsoft .NET Runtime - 6.0.14 (x64)
Regards, Jaap.
The current version of the .NET 6 runtime is 6.0.22, so you're a few versions (and security updates) behind.
https://dotnet.microsoft.com/en-us/download/dotnet/6.0
Not sure why you have two entries for the 6.0.14 runtime, but I would uninstall it and install 6.0.22.
If that doesn't solve the /auto issue, do a repair install of Windows 11 using the In-Place Upgrade method.
As mentioned, do a full drive image first.
Hello OldNavyGuy,
I've uninstalled .Net 6.0.14 and installed 6.0.22, then rebooted the PC. No change.
As DISM and SFC report no corruption, I'll wait awhile before I try the in-place upgrade. At the moment, it feels like using a sledgehammer instead of a toothpick, if you get my meaning :D .
Thanks for responding!
Regards, Jaap.
Corruption is not the only cause of Windows-related issues.
Another way of looking at it is the time spent troubleshooting, versus how long it takes to do a full drive image and then an in-place upgrade.
Your call.
Good luck.
Quote from: Jaap on October 08, 2023, 12:33:11 PMHello OldNavyGuy,
I've uninstalled .Net 6.0.14 and installed 6.0.22, then rebooted the PC. No change.
As DISM and SFC report no corruption, I'll wait awhile before I try the in-place upgrade. At the moment, it feels like using a sledgehammer instead of a toothpick, if you get my meaning :D .
Thanks for responding!
Regards, Jaap.
Same happens to me, but on windows 10 using net framework 7
To me, it shows the pop up when I click update apps, and it update all apps anyways if I press continue.
If you want to do a deep dive, download Sysinternals ProcDump, and set it up to generate a crash dump when the issue occurs.
https://learn.microsoft.com/en-us/sysinternals/downloads/procdump
Then, get WinDbg, and use that to analyze the crash dump file.
https://learn.microsoft.com/en-us/windows-hardware/drivers/debugger/
Thanks for your suggestions, your time and your trouble, OldNavyGuy!