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

Recent posts

#21
There was nothing in the Apps/Programs & Features list with that exact version.
However, a search for 140.0.80.000 in the registry found it in a few locations, all linked to "HP Scanning", which looked to be part of an old HP printer driver.
Said HP printer driver bundle was in the Add/Remove Programs as version 14.0. I uninstalled it, but no change.

I then started manually deleting keys from the registry and checking PMPC each time a key was deleted. Farbar finally went away when I deleted the key located in:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall
#22
Can you please check what app has the version of 140.0.80.000 in "Add/Remove Programs" and let me know?
#23
Testing the latest version on multiple machines, one is showing this in the My Apps list, but I've never installed it, much less through PMPC and neither the app nor the installer for this app exist anywhere on this machine.

FRST.jpg

I would like to know why it's being detected and where PMPC thinks it is located, but there is no other info available.

Thank you!

#24
Scheduled task updating only works if "When opening PMPC, automatically start updating outdated apps" is enabled.  I think a different toggle here would be helpful, mostly because I don't want apps to start updating just because I opened the GUI.  I may be checking on an issue and don't want to make it worse.  Maybe a troubleshooting commandline switch that opens PMPC with default settings (nothing automatic)?
#25
Thanks Andrew. I just wish MS would leave things alone and stop making more work for us.
#26
I'm attempting to have Microsoft correct this mistake here: https://github.com/MicrosoftEdge/WebView2Feedback/issues/4931#issuecomment-2480259132 if you have a github account, please vote on my post and/or make a comment of your own, they can hide the app from ARP without messing up detection for everyone.
#27
So happy I found this post as I've already spent so much time on WebView2. Unfortunately, according to this link, WV2 will no longer appear in the installed apps list.
https://learn.microsoft.com/en-us/deployedge/microsoft-edge-relnote-stable-channel#announcement

WV2 has been such a pain for me, after provisioning/autopilot is complete and the user logs in, apps like Global Protect and Teams install. However, both Global Protect and Teams require WV2. Both apps fail because not being able to find WV2 although I can find WV2 in the registry.
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\EdgeUpdate\Clients\{F3017226-FE2A-4295-8BDF-00C3A9A7E4C5}

Has anyone else struggled with this and hopefully found a solution?
#28
General Questions (Free Home Updater) / Re: portable apps
Last post by dking02 - November 15, 2024, 04:41:13 PM
As a follow-up to my preceding reply ---

For simplicity, I only mentioned a single location (folder) for downloading the package (.exe or .zip file) for a portable app. That's the way I have Home Updater V5 set up. I then just copy the downloaded .exe file or expand the downloaded .zip file to the desired folder or subfolder where I "install" the portable app.

If you are not satisfied with downloading portable packages to a common portables location, you can set the location where the package for a particular app will be downloaded by changing the portables location setting in the Home Updater console on the Apps tab when installing the app. I believe the PMPC server records the initial download location at the time of the install of each portable app so that subsequent updates or re-downloads of the app can be downloaded to the same location without the user having to check or change the current setting of the portables location. However, changing the download location for individual apps means more complex settings in PMPC Home Updater and dependencies on them.
#29
Thanks Andrew!
#30
Unfortunately, it won't matter which version you deploy. It seems like the version on the machine auto-updates to the latest broken version before our version even has a chance to attempt to install, so the installation will return a failure at the moment. It seems Microsoft is aware of the issue, and I am hoping they pull that update soon.