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

Recent posts

#21
Found it under the Scheduler tab.
Strange that it enabled itself for no reason. This should be opt-in by default.
#23
Given the disappointing lack of a single response (0 out of 69 views at the time of this reply) to this simple request for other users to check if they were also seeing the same error message in their log files, I resorted to locating a recent post on another topic where the originator had attached a diagnostic .zip file. The included log file showed the same error occurring frequently beginning on 2026-05-04, about one week after updating to v5.4.4.0 and continuing to the end of their log file on 27-Jul-2026. This indicates that this error message is likely systemic and warrants an explanation or correction by the PMPC staff.

Therefore, PMPC staff please respond.

#24
Are other users seeing the following 'Access denied to local.dat' error message in their Home Updater .log file?

    ERROR  Failed to write bytes due to an error: Access to the path 'C:\ProgramData\PatchMyPC\local.dat' is denied.

I happened to notice many instances of this message on multiple machines while trying to track down another but apparently unrelated issue. The error appears to be harmless but started to appear on or about 16-Apr-2026 which coincides with the release of Home Updater version 5.4.4.0. Both the log file and the local.dat file referenced in the error message are located in the Logs Folder (default = C:\ProgramData\PatchMyPC\) which can be accessed via the 'View Logs Folder' button at the bottom right of the Home Updater 'About' panel.

Sample excerpt from .log file
[2026-08-29 00:00:02]  INFO  Started application v.5.4.5.0
[2026-08-29 00:00:02]  INFO  Updater.ini is valid and up to date.
[2026-08-29 00:00:02]  INFO  Protocol homeupdater registered successfully.
[2026-08-29 00:00:03]  INFO  Check Apps from Scheduled Task has been started.
[2026-08-29 00:00:03]  ERROR  Failed to write bytes due to an error: Access to the path 'C:\ProgramData\PatchMyPC\local.dat' is denied.
[2026-08-29 00:00:03]  INFO  Notify user about 1 outdated app(s).
[2026-08-29 00:00:33]  INFO  Notification was dismissed by timeout (30000 seconds)
[2026-08-29 00:00:33]  INFO  Check Apps from Scheduled Task has been finished.
[2026-08-29 02:00:02]  INFO  Started application v.5.4.5.0
[2026-08-29 02:00:02]  INFO  Updater.ini is valid and up to date.
[2026-08-29 02:00:02]  INFO  Protocol homeupdater registered successfully.
[2026-08-29 02:00:02]  INFO  Check Apps from Scheduled Task has been started.
[2026-08-29 02:00:03]  ERROR  Failed to write bytes due to an error: Access to the path 'C:\ProgramData\PatchMyPC\local.dat' is denied.
[2026-08-29 02:00:03]  INFO  Notify user about 1 outdated app(s).
[2026-08-29 02:00:33]  INFO  Notification was dismissed by timeout (30000 seconds)
[2026-08-29 02:00:34]  INFO  Check Apps from Scheduled Task has been finished.
[2026-08-29 02:08:19]  INFO  Started application v.5.4.5.0
[2026-08-29 02:08:19]  INFO  Updater.ini is valid and up to date.
[2026-08-29 02:08:19]  INFO  Protocol homeupdater registered successfully.
[2026-08-29 02:08:19]  DEBUG  View MainViewModel has been loaded
[2026-08-29 02:08:19]  INFO  Started [Apps Catalog loading] operation...
[2026-08-29 02:08:20]  ERROR  Failed to write bytes due to an error: Access to the path 'C:\ProgramData\PatchMyPC\local.dat' is denied.
[2026-08-29 02:08:21]  DEBUG  View InstalledApplicationTabViewModel has been loaded
[2026-08-29 02:08:21]  INFO  [Apps Catalog loading] operation has been completed. Execution time: 1.3507729 seconds.

#25
My original post identified limitations of Home Updater when dealing with apps like Visual Studio Code and PowerToys that offer system level (machine-wide) or user level installations.

Resolution: Since Home Updater only supports system level installations and updates of such programs, I uninstalled any existing user level instances and replaced them with system level installations in order to provide compatibility with Home Updater. If these programs are ever installed or updated outside of Home Updater, the user must take care to download the system level setup file for the program to establish or maintain compatibility with Home Updater. This resolution assumes no changes to Home Updater.
#26
Hello!

We are using the MUI of Acrobat 64-Bit so it can work better for everyone.
If you are downloading a language specific Acrobat or the 32-Bit from the website, then it will not be detected by Patch My PC.
#27
Hi all this has to do with patchmypc home updater free version. I have this on a USB stick.
My laptop is running windows 11 pro I have an older version of Adobe acrobat installed on the laptop. I download the full .exe file from the adobe website and installed fine. I put in my usb stick into laptop and do a scan of the programs installed on laptop to see if it can pick up any dates. It picks up all my other programs on my laptop except Adobe acrobat.

What I do then is I uninstall Adobe acrobat completely and put in the patchmypc usb stick. I search for adobe acrobat to install it installs perfectly. Then the patchmypc usb actually picks up adobe reader as installed on my laptop.

So I am just wondering why when i download the .exe file from the adobe site and install it patchmypc usb wont pick it up but yet when I install it from the patchmypc usb it does.

It did work before in that when I installed it from the site and installed it patchmypc would pick it up fine seven letting me know of any update pending so i have no idea what has happened in the mean time
#28
I'm unable to patch three programs on Windows 10 Pro (64 bit). I'm receiving this message: Alert. We are sorry, but there was an error. Message: Value cannot be null. (Parameter 'Path1'). The programs that cannot update are: DesktopOK (x64), Display Driver Uninstaller, and Tor Browser.

I reset all settings to default. I uninstalled Patch My PC Home Updater with Revo Uninstaller, rebooted, then installed Patch My PC Home Updater. This did not fix the problem.
#29
Typically you want to use the setup.exe as it handles the installation of all components and will call the msi during installation.

We do have this KB Article for packaging CC apps as Custom Apps that may help.
https://patchmypc.com/kb/package-an-adobe-creative-cloud-app-as-a-custom-app/
#30
This is about Adobe Creative Cloud licensed products for environments with Adobe Admin Consoles (which is our setup). Installer packages for Creative Cloud products generate an archive file. Expanding the archive file contains an MSI, but also a setup.exe and a bunch of supporting files. Is there a process or methodology? Has anyone had success? I have a support ticket in with Adobe, but Patch My PC's cloud-packaging seems like something Adobe would not be familiar with. Does Patch My PC have a Marketing department (and an Adobe Admin Console)? Would love to know how this could be done.