Messages

Try downloading and installing the ARM64 version of the 8.0.11 Desktop runtime...

https://dotnet.microsoft.com/en-us/download/dotnet/8.0

Try downloading and installing the ARM64 version of the 8.0.11 Desktop runtime...

https://dotnet.microsoft.com/en-us/download/dotnet/8.0

The Desktop Runtime is a separate download...

https://dotnet.microsoft.com/en-us/download/dotnet/8.0

Thanks for the request. For new feature requests, we are shifting things over to our ideas portal. I coverted this request to a new idea at: https://ideas.patchmypc.com/ideas/PATCHMYPC-I-5108

If you would like to see this added, could you please submit an idea there instead?

I guess I don't see it as a "new feature".

It was a working feature in v4 that was not included in v5.

I am asking that the v4 functionality be restored.

Hey OldNavyGuy,

Thanks for bringing this to our attention. We're looking into the setting for disabling silent installations to see if there's a bug causing the behavior you're experiencing.

About the installer being deleted after you exit—could you let us know how retaining the installer file helps in your workflow? Understanding your use case will help us improve the app.

Appreciate your feedback!

The "Enable Download Only Mode" in v4 worked perfectly for our needs.

Multiple computers on the home LAN that use the same app can use a single installer. No need to run PMPC to download and install on each computer.

Testing before deploying an update. There have been cases when an update did not go well. Easier to undo one install than multiple installs.

PMPC installers are archived, and updated. If a clean install is necessary, apps are ready for re-install, rather than re-downloading each app.

There was also the "Don't Delete App Installer Files" setting in v4, but we didn't use it. However, I could see it being useful for some (saves a manual install, but keeps the installer) for similar reasons.

 

+1 for export function.

Consider adding options for Windows System, Light, and Dark.

Can't really see an upside to renaming the executable...

Most folks are just going to click on a Desktop shortcut, or the Start menu entry, and run the app.

They won't really care what the EXE is called.

All the version 5 stuff has been cleaned up.

Run the version 5 uninstaller.

You should easily see the issue.

1366 x 768 is the recommended display resolution for this particular laptop.

And, no...it doesn't create issues everywhere.

Scaling at 125% works well for all other apps on that system.

It's off on my install, but that's not the way it worked.

When I selected an app that was out of date, it kicked off the installer, and updated the app.

I was expecting it to download the installer to the location I specified, and stop right there.

Which is the behavior in version 4...

Uninstalled version 5.

As mentioned, the version 5 uninstaller leaves the Self Update Scheduled Task on the system, instead of removing it.

I used Revo (one way to do it) to delete that task.

Resolution is 1366 x 768, and 125% scaling.

No issues with any other app.

Windows 10 22H2.

It is weird, but I uninstalled version 5 on 2 machines, and will go back to version 4 until the next release.

Someone else will probably pop up with a similar issue.

What I posted is pretty much it...

No option to globally turn off automatic updating like version 4.

Disabling the global Silent Install option in settings doesn't.

You'll get to see the app installer (because it's not a silent install), but exiting out of the installer itself will delete the installer executable.

Used Revo Uninstaller Pro to remove it.