Jump to content
Piriform Community Forums

Edkiefer

Members
  • Content count

    3
  • Joined

  • Last visited

Community Reputation

0 Neutral

About Edkiefer

  • Rank
    Newbie
  1. possible Application Paths Issue bug

    Thanks for link, I will read it. No, its Win19 1703 but it was a upgrade from Win7. I could easy test on native win10 VM 1709 I have too. Ok, did quick check in VM 1709 and there no system32 paths, the paths I checked so far were all ok (got a lot of Onedrive ones as it seems to get updated often)
  2. possible Application Paths Issue bug

    I get that, I didn't post this for my part but for others, if it is true bug. Many still will use the option and not check stuff. I only run it to see and I do remove app path as I DL many programs and then clear the old ones (these are installers).
  3. Running the registry cleaner, Application Paths Issue I found a few entry's were the path of exe is correct (I always check to see if path is right before deleting). here is the few were exe was there, Bold is checked path. Application Paths Issue C:\Windows\System32\UNPUXWorker.exe HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Store Application Paths Issue C:\Windows\System32\UNP\UNPUXLauncher.exe HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Store Application Paths Issue C:\Windows\System32\MRT.exe HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Store Application Paths Issue C:\Program Files (x86)\Malwarebytes' Anti-Malware\unins000.exe HKCU\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Compatibility Assistant\Persisted They all seem to be in the compatibility assistant area section.
×