• Welcome to Support Forum: Get Support for Patch My PC Products and Services.
 

Recent posts

#2
Hi @Conny Lindqvist,

Unfortunately, the vendor offers an MSI installer for the Keeper Password Manager application for the 32-bit version only. The 64-bit version is an MSIX bundle, which our solutions currently do not support. Adding support for MSIX based installers is something that's on our radar, but that we haven't added to our roadmap just yet.

If you like, you can upvote one or more feature suggestions that were submitted for this:


This ensures you will receive a notification if/when the status of the suggestion(s) you upvoted changes.
#3
Quote from: dking02 on April 20, 2025, 01:52:12 AMActually there are 49 non-portable apps which are missing their Publisher/Vendor name. Additionally, all 99 portable apps in the Apps Library are missing this data.

See the following attachment (.pdf) for the full list of the currently affected apps:
Home Updater Apps Missing Vendor Data.pdf 
This was done on purpose since the vendors of these app they either changing their Publisher name with every few releases, or they don't have a Publisher name at all, and we have to leave it empty in any way so the apps can actually get detected.
#4
Actually there are 49 non-portable apps which are missing their Publisher/Vendor name. Additionally, all 99 portable apps in the Apps Library are missing this data.

See the following attachment (.pdf) for the full list of the currently affected apps:
Home Updater Apps Missing Vendor Data.pdf 
#5
Note on Step 3 in the instructions:

Rather than navigating to the wbem directory using Windows Explorer (the path is kinda garbled), simply copy...

C:\Windows\System32\wbem

...open a Run box, paste it in, and click OK.
#7
I have two systems with the same hardware and each running Windows 10 Home 64 bit(latest updates), on one system, PatchMyPC Home Updater v.5.1.3.0 runs fine, the other, I get this message when starting:

Alert   We are sorry, but there was an error.
Message: Invalid Class

Why?
#8
I think Justin would like you to right-click on those registry locations, and select Permissions.

Click on each entry (user name or group) in the upper section, and note the permissions in the lower section.

Post the results.
#9
Hi Justin,
Thanks for getting back to me. 

- Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall
- Computer\HKEY_CURRENT_USER\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall
- Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall
- Computer\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall

I checked all 4 entries in regedit and they all came back with the data column showing (value not set).  Does this answer your question, and if so, what's my next move?  Just so you know, I am logged in as an administrator in WIN10.  I am definitely not a coder, but I have some experience searching and resolving registry issues with guidance!  Thanks again for your time and effort! 
#10
Could you let us know the permissions on the following registry keys using RegEdit.exe?

 - Computer\HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall
 - Computer\HKEY_CURRENT_USER\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall
 - Computer\HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Uninstall
 - Computer\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall
 
The reason I'm asking is that I was able to reproduce this issue on our custom reg key after I set 'Deny' on read/write permissions for it.
 
So most likely, the user does not have read permission on these keys and/or their subkeys.