You need to understand what patching and your log returns actually mean before basing your post and assumptions on baseless accusations.

Just because one file is or is not patched here will not be the cause of a popup, especially when your log returns prove that the app is already patched.

Some files are left in intentionally for backwards compatibility so that they are covered in older versions; however, that does not mean they still need to be patched in latter versions.

Additionally, where the log returns “File already patched by GenP” and clearly shows “Patched”, that means the file has already been patched and therefore does not get overwritten again.

If you simply click Search and Patch multiple times, nothing will happen after the first run as it only patches once.

To get the files back to their original state, you need to Restore first and then Patch again.

Still have issues after restoring the app and patching again, then simply do a clean uninstall of the specific app and remove any leftover app folder remnants, then simply reinstall and patch as clean again.

A basic understanding of how things work, which can be achieved by following the provided guides instead of relying on assumptions, would be helpful.

As for the unlicensed popup, that can happen to anybody at any time and is not just attributed to one single reason, especially when you do not provide your full log.

Alongside Adobe’s multiple methods for triggering it, yours can easily be caused by a plethora of reasons on your own side and have nothing to do with GenP.

As for the popup itself, it is already well covered in the troubleshooting section; you just need to follow it like most others do.

Use the GenP Wiki and follow the guides for it, make sure you follow them properly as it clearly tells you what to do if the CC app is showing trial or buy now instead of install.

Use the Troubleshoot Section and simply follow the steps for the Unlicensed (Non-AGS) popup, no need for new account or full clean if guide sections are followed properly.

Already answered: https://lemmy.dbzer0.com/post/69179905

What does and what does not get modified is intentional, if you want to alter it you are free to do so, however no help and support will be provided.

The issues you’re experiencing are generally related to incomplete patching, corrupted application states, incorrect setup procedures, leftover configuration data, or mixing outdated methods with newer releases.

Properly patched and clean installations using the correct version of GenP are not showing these problems in testing.

For example, Photoshop v27.7 patched with GenP v4.0.4 works without issues, and the home screen displays normally. If there were a widespread problem like a blank home screen, the release would not have been published.

Since you’ve patched using multiple GenP versions (from v4.0.0 to v4.0.4), it’s essential that the guides were followed fully and correctly.

GenP v4.0.2 and onward introduced new methods that must be set up properly before patching.

There are differences in the patched files between versions, and these are intentional and necessary. Skipping or canceling parts of the patch process can break functionality and lead to issues like the one you’re experiencing.

Some files are included to support older versions and assist with user progression, but not everything listed needs to be patched; GenP automatically handles what is required and leaves unnecessary files untouched.

If you manually interfere with the process or selectively skip files, you can break the application yourself.

At this point, the most reliable fix is to fully uninstall and reinstall, then carefully follow the guide step-by-step using the latest GenP version.

In my testing of the latest Photoshop and Photoshop Beta releases across three completely different systems, all were installed and configured correctly, working as expected with no popups or blank home screen issues.

I also ran WinTrust on both the General and Beta versions after installation without any problems. The automated hosts setup works correctly, although it was not required and was therefore removed.

Firewall rules should only be used as a last resort, as they are unnecessary on properly configured systems.

As long as the latest setup is applied correctly with a clean configuration state, there should be no issues. Some users may need to uninstall and reinstall the application if incorrect setup steps or a corrupted state have affected the installation.

That is why it’s crucial to follow the provided guides carefully rather than assuming prior steps are already correct.

Lightroom CC has never been supported because it is a cloud-based app, whereas Lightroom Classic is a desktop-based app and is fully supported.

This is already clearly mentioned in the Compatibility List and the GenP Setup, Troubleshooting, and Best Practices Guide if you refer to them.

Otherwise, Lightroom Classic runs perfectly when patched with the latest GenP. If you encounter popups, follow the Troubleshoot Section for the specific popup being shown.

Nope, this is not a GenP issue, so there is nothing for GenP to fix here.

Acrobat performs a first-run entitlement check after patching. If that check cannot complete successfully, Acrobat will remain stuck on “Fetching your subscription details”.

GenP patches licensing locally, but it does not interfere with Adobe’s entitlement handshake process. This is already explained in the GenP Setup, Troubleshooting, and Best Practices Guide if you refer to it.

You just do what most other people have done, read the guide fully, as it already explains it.

If one link doesn’t work, use the alternative link instead.

The issue is straightforward: your firewall settings have been too restrictive.

Blocking all Adobe-related processes is unnecessary and can cause significant problems.

It’s likely that either your antivirus has interfered with the prepatched files, which the old WhiteDeath crack (albeit called differently now, but still the same old method used) applied after Acrobat installation.

Or manual intervention is required to properly patch them yourself using the old crack method provided.

Otherwise, your antivirus may have quarantined a prepatched Adobe file, which now needs to be excluded.

Additionally, Monkrus renames Adobe crash reporter files by adding a .bak extension.

- Spyware modules Log Transport Application, CRLog Transport Application and Adobe Crash Processor have been disabled.

While he labels these files as spyware, they are actually just crash reporting modules, and as a result, crash reports provide no feedback to help diagnose issues.

For more detailed guidance, refer to Monkrus own page for Acrobat and the FAQ Section on the torrent tracker.

GenP doesn’t need an update for this.

Monkrus releases are essentially prepatched using the same underlying methods, just packaged as standalone installers. Because of that, the setup and install environment can differ slightly compared to doing a normal install and patching it yourself with GenP.

So a repack working doesn’t confirm an issue with GenP, it usually points more toward a difference in setup or configuration on your side rather than a problem with the patching itself.

As already mentioned in my previous reply, there are no issues with Media Encoder or GenP, the issue is on your end.

You’ve listed multiple steps, but you’ve clearly skipped key parts of the Troubleshoot section.

There’s no mention of creating a new verified Adobe account, signing out of the CC app, signing back in, and then repatching both the CC app and your individual apps. That step alone resolves many free trial popup issues.

You also didn’t mention simply closing the popup or accepting the trial and continuing, which, when everything is patched correctly, does not affect functionality.

On top of that, you stated you used an older GenP version (from 4.0.0 to v3.7.1), meaning you actually regressed instead of using the latest version (v4.0.3), which most users ensure they are running.

Your claim that v3.7.1 works while v4.0.0 does not isn’t valid either, nothing for Media Encoder changed between those versions, and both use the same patching methods. So that difference does not prove anything in terms of functionality.

If you believe there is an issue, you should be providing your patch log output. That clearly shows what was and wasn’t patched and helps identify or clarify any actual problem instead of relying on assumptions.

All of this is already covered in the guide, and if followed properly, the issue should not persist.

There are no issues with Media Encoder.

If you had followed all steps in the Troubleshoot Section, then the last thing you would have done would have covered it as a last resort, although if all patched properly then free trials should not be appearing.

Your claim isn’t valid either, nothing for Media Encoder changed between versions, and both use the same patching methods. So that difference does not prove anything in terms of functionality.

If you believe there is an issue, you should be providing your patch log output. That clearly shows what was and wasn’t patched and helps identify or clarify any actual problem instead of relying on assumptions.

Yes, as long as keep it in the self contained folder.

Or, just take Source as it is and then just rebuild it on another device.

Or just grab v4.0.3…

That is all covered within the GenP Guides, disable your used anitvirus when downloading.

Otherwise, whitelist when you have it downloaded so it is allowed, all as mentioned in the guides provided.

There are no issues with Media Encoder.

If you had followed all steps in the Troubleshoot Section, then the last thing you would have done would have covered it as a last resort, although if all patched properly then free trials should not be appearing.

As already mentioned, well covered in the Troubleshoot Section under CC App Errors.

Most likely you are not using the latest version of GenP available to you.

Refer to the Compatibility List and GenP Guides for more detailed information.

Otherwise, there are no issues with patching Photoshop using GenP.

If you’re still experiencing issues, it’s likely related to the app itself or your system setup, rather than a problem with GenP.