[–] [M] 1 point 11 months ago* (last edited 11 months ago)

There are no issues with InDesign (latest or earlier versions) when patched with the latest GenP.

If any problems existed, they would be documented in the Compatibility List and mentioned in the Announcements channel on GenP Stoat.

For reference, InDesign v21.0.2 works perfectly when patched with GenP v3.7.1, and there are no issues related to it closing immediately upon opening.

It's worth noting that I have been updating my own InDesign up to v21.0.2, repatching with GenP v3.7.1, all without any issues.

If this were a common problem caused by GenP, others would be reporting similar crashes, which they are not.

Therefore, the crash after patching may be due to specific system or environment factors rather than the patch itself.

InDesign crashing immediately on launch is usually caused by corrupted background Adobe processes, blocked components, or damaged preference files.

It can also happen if antivirus software is scanning or blocking InDesign during startup.

The process still in use issue can often be resolved by fully closing all Adobe processes in Task Manager and then restarting.

Resetting InDesign preferences, clearing its cache folders, and ensuring CC services are running properly can also fix sudden-close issues.

If the problem persists, performing a clean reinstall is recommended, as leftover or inconsistent files can trigger launch failures.

  • source
  • [–] [M] 1 point 11 months ago* (last edited 11 months ago)

    This is already addressed in the Compatibility List and has also been discussed in the GenP Stoat channels. Beta versions are not officially supported beyond simply being installable.

    If you encounter problems with the latest Beta release, make sure that both the CC app and the individual Beta apps are correctly installed, updated and patched.

    If the problem persists, your options are to roll back to an earlier Beta release or use the stable General Release instead.

    Additionally, as noted in the Compatibility List, Beta versions are experimental builds designed for testing and feedback.

    Adobe may change or break functionality at any time, sometimes even through silent or forced updates, which makes Beta software inherently unstable.

    Because of this, GenP does not provide support for Beta apps, and any issues arising from Beta builds fall outside their scope.

    If you choose to work with Beta versions, please be aware that you do so at your own discretion.

    Should a genuine compatibility issue ever arise, it would only be addressed in a future general release, never through a standalone fix developed specifically for a Beta build.

  • source
  • [–] [M] 1 point 11 months ago*

    First of all, you don't use GenP to download anything from Adobe. Adobe apps are downloaded directly from Adobe's servers, and GenP is only a patcher that modifies your installed files to bypass subscription requirements.

    All of your issues are already covered in the GenP Guides and Troubleshoot Section. You should refer to those instructions and follow the recommended steps.

    If the CC app is installed and patched correctly as per the GenP Guide, then you only need to patch or repatch individual apps as needed. You can remove the search for the CC app itself in GenP options once it’s properly patched and working, this is explained in the guide.

    Once the CC app is patched and shows Install instead of Free Trial or Buy, you’re free to install new apps or update existing ones. After installing or updating, simply use GenP to patch or repatch the individual apps, making sure to unpack (where required) before patching.

    When the CC app is patched and functioning correctly, it behaves as if you have a genuine subscription. You can have the CC app open or closed during individual app installs/updates, or patching/repatching with GenP without issues.

    Be aware that if the CC app, or any of the individual apps aren't properly patched, or if you haven't followed the guide steps, you may encounter issues like apps closing unexpectedly.

    Apart from improper patching with GenP, issues such as Premiere Pro closing shortly after opening can result from a variety of system-related problems.

    These may include version incompatibilities between Adobe apps, a corrupted or incomplete installation, damaged preferences or cache files, conflicting or outdated GPU drivers, insufficient system resources (such as RAM or disk space), missing or outdated Visual C++ runtimes and other essential system libraries, conflicts with third-party plugins or extensions, incompatible operating system updates, or restrictions imposed by antivirus or firewall software.

    In some cases, corrupted media cache or project files can also prevent the app from launching properly.

    Note that we do not provide support or troubleshooting for Adobe system issues; our guidance is focused solely on the GenP patching process. For detailed instructions or help with app- or system-related problems, post on the app’s own Subreddit or search the Adobe Community for similar discussions.

    For all GenP-related issues, you can refer to the GenP Wiki. If all steps are followed correctly, your apps should run smoothly. Persistent problems are likely caused by system or installation issues beyond our scope.

  • source
  • [–] [M] 2 points 11 months ago

    Monkrus is simply prepatched with GenP files. If you encounter a non-AGS-related popup and have blocked the app in your firewall, then you shouldn't experience any issues with popups appearing.

    If the popup still appears, you may not have blocked the app correctly in your firewall, or you might have only blocked the shortcut instead of the actual app.

    Regarding switching between GenP and Monkrus, this process is well documented in the GenP Wiki and its relevant guide sections. Although Monkrus is prepatched with GenP files, it operates differently because it doesn't require the CC app.

    Therefore, if you want to switch from Monkrus to GenP or vice versa, you should follow Guide #4: Full Clean. This involves removing all Adobe apps using your current method, then doing a full and clean install of Adobe through the alternative method.

    Never mix and match GenP and Monkrus; always perform a full clean before switching to ensure proper functionality and avoid conflicts.

    Uninstalling Adobe apps does not delete your Premiere Pro projects, After Effects compositions, Photoshop files, preferences, templates, LUTs, or any other content you created or saved separately. Those files stay exactly where they are.

    However, you won’t be able to open or edit them until the relevant Adobe app is installed again. Once the program is reinstalled, your project files should open normally, as long as you’re installing a compatible version of the software.

    If the new installation is a different major version, the project may need to be upgraded, but the app will prompt you before making any changes.

    Safely backing up your project files mainly comes down to keeping copies of your project folders, media, and any custom assets in a separate location, such as an external drive or cloud storage.

    Presets, plugins, and custom settings can usually be preserved by manually copying their folders before uninstalling anything, since many of them sit in your user-profile directories rather than the application folder itself.

    Version compatibility issues can be avoided by reinstalling the same major version you were using before, or by keeping a backup of the original project file in case the newer version needs to convert it.

  • source
  • [–] [M] 1 point 1 year ago*

    Your own GenP.exe ran correctly on your system, but it wasn’t able to download the blocklist from the server it normally connects to.

    Because the blocklist couldn’t be retrieved, the script marked GenP’s output as invalid and then tried the backup URLs.

    Those backup sources also failed to load, which means your network or ISP is blocking all of the domains used for fetching the updated hosts entries.

    Since no valid blocklist could be retrieved from any source, the script automatically restored your hosts file to the previous backup to prevent writing an empty or incomplete file.

    That’s why the hosts file returned to its original state.

    To fix this, make sure your network can access the domains used by GenP and the fallback URLs.

    Using a VPN or changing your DNS (for example to Cloudflare 1.1.1.1 or Google 8.8.8.8) usually resolves the issue.

    Security software such as antivirus HTTPS filtering can also cause this problem, so temporarily disabling that may help as well.

    The advanced script works perfectly as long as GenP can reach the latest domain list, or, if that fails, any of the backup URLs remain accessible on your network or through your ISP.

    This situation is also mentioned in the Advanced Method section of the GenP guides, which explains the connection requirements and what to check if the script cannot retrieve the blocklist.

  • source
  • [–] 1 point 1 year ago

    I've been having the same issue on the Advanced method Host File updater, keeps saying that on the log. I made sure to change the GenP file path to where GenP is in my Downloads (C Drive) and I made sure the folder and Downloads itself has full admin access on all my admin accounts.

    But the updater task works just fine when it uses the backup URLS, so I've kinda just let it be since it still works. Plus since I've now started using Wintrust on Premiere and Photoshop (Acrobat blocks popups great just patching with GenP), I've not really used the hosts file anymore anyway.

  • source
  • You don’t need to worry, the three-hour check used by the Advanced Method is extremely lightweight and won’t affect your computer’s performance under normal conditions.

    Even on older systems, the task only runs briefly and uses minimal CPU and memory, so it won’t slow down your computer.

    If you’re still concerned about performance, then the Advanced Method might be more than you need.

    In that case, it’s better to use the Basic Method, which performs a simple once-daily update and avoids the extra checks and validation steps.

    And honestly, if a simple scheduled task is noticeably affecting your system, it’s time to consider updating your device!

  • source
  • [–] [M] 2 points 1 year ago* (last edited 1 year ago)

    This isn’t actually a bug with the CC app. The repeated update reminder happens when the CC app’s update hasn’t fully finished before the app is closed or modified. Although it may look like the update has completed, the CC app often finalises key components only after the app is reopened once.

    If that first-run stage is skipped or interrupted, the CC app detects inconsistencies in its own files on the next launch and assumes the update is incomplete, which leads to the constant update loop you’re seeing even though you’re already on the latest version.

    The Troubleshoot Section does cover this under CC App Errors as well. It explains that after updating CC, the app needs to be opened again so it can complete its internal setup. Only once that process is done should the app be properly quit and patched.

    If this sequence isn’t followed, the CC app may attempt to self-repair on the next launch, revert some of the updated components, and start prompting for the same update over and over again because it believes the previous update didn’t finish.

    This also explains why you might see a message indicating that the app is already patched or already modified. If the update’s finalisation step hasn’t completed, CC may still request an update even though the log says everything has already been applied.

    The app isn’t reacting to the modification, it’s reacting to the fact that the underlying update never finished its first-run completion, so it keeps trying to restore its expected state.

    Adobe also enforces CC app updates even if automatic updates are turned off. The CC app must stay current because it manages all Adobe apps, syncs preferences and settings, provides cloud features, handles fonts and storage, and maintains compatibility across services.

    Once a version becomes too outdated, Adobe blocks older releases from cloud access, which is why CC continues insisting on updates regardless of your preferences.

    If the reminder continues even after allowing CC to finish its update and reopening it properly, the next step is to repair or reinstall the CC app. Adobe’s own support pages explains how to do this, and the Troubleshoot Section outlines the same process.

    Just keep in mind that this is a community forum and not Adobe Support, so the guidance is based on general Creative Cloud behaviour rather than internal diagnostics.

  • source
  • [–] [M] 1 point 1 year ago*

    This is already covered in the Compatibility List and the GenP Setup, Troubleshooting, and Best Practices Guide, as well as discussed extensively in the GenP Stoat channels.

    We don’t provide support for Lightroom CC, as it is a cloud-based application. Because it relies on Adobe’s online services, its behavior can vary widely between users.

    For some, it may work without any issues; for others, it might work only temporarily, with certain features failing over time, while some users may experience constant trial notice, non-AGS-related popups or find the app won’t run at all.

    Reinstalling or patching Lightroom CC can also cause it to malfunction, since it depends on online authentication, background Adobe services, and synced configurations to function correctly.

    The only recommended solution is to use Lightroom Classic, which is fully desktop-based and fully supported.

  • source
  • [–] [M] 4 points 1 year ago*

    Everything you need to know about GenP is already covered in the GenP Wiki, GenP Guides, and GenP Setup, Troubleshooting, and Best Practices Guide.

    These resources thoroughly explain why false positives are common with GenP, which is simply just a patcher that modifies app files. It's important to understand that antivirus scans, such as VirusTotal, often flag such tools because they perform actions similar to malicious software, like altering files or bypassing protections. This behaviour is typical and expected for patchers and does not indicate that the tool is malicious.

    Many detection engines used to simply label false positives for GenP as HackTool or Patcher. However, over time, started assigning a wider variety of names and classifications, often based on the behaviour of the tool rather than anything malicious. The source code for GenP is publicly available, allowing anyone concerned to review it directly. If you still have doubts, you can verify the code yourself or consult the official guides for detailed explanations.

    It is worth noting too that VirusTotal aggregates results from many antivirus vendors, each using different detection methods. A high detection rate does not necessarily mean the file is harmful; many engines will simply flag GenP's patching activities due to their behavioural signatures. Repackaged versions from Monkrus, are still based on GenP and will typically trigger similar flags.

    If you are genuinely concerned about safety, the best course is to avoid non-genuine methods altogether and obtain software directly from Adobe with a legitimate subscription.

    In summary:

    • GenP itself is not malicious.
    • False positives are normal for patchers due to their nature.
    • Detection rates can increase as the tool evolves.
    • Always verify the source and consider whitelisting GenP in your antivirus if you trust it.
    • Or use genuine software for peace of mind.

    Everything you need to understand this situation is already explained in the guides.

  • source
  • [–] [M] 3 points 1 year ago* (last edited 1 year ago)

    Make sure you are using the latest GenP version; older versions won't work properly.

    Your log shows that you are attempting to unpack and patch Premiere Pro files that have already been unpacked and patched.

    The UPX error code 2 simply indicates there is nothing left to unpack, and messages like No patterns were found or file already patched confirm that the files are already patched.

    GenP does not overwrite previously patched files, patching is a one-time process per file. To fully unpack RuntimeInstaller.dll again properly, you would need to uninstall Premiere Pro, reinstall it to restore the original packed RuntimeInstaller.dll file, and then use GenP to unpack and patch them properly.

    For all other files, you can use the Restore function in GenP to revert them to their original state. Note that RuntimeInstaller.dll will remain unpacked if it was previously unpacked, it cannot be repacked.

    The safest way to ensure proper unpacking and patching is to uninstall Premiere Pro and After Effects, reinstall them, and then run GenP to unpack and patch correctly.

    If non-AGS-related popups appear after unpacking and patching properly, then you have these options:

    Use WinTrust (Premiere Pro only/not After Effects), or repatch the apps with the modified GenP v3.7.1+Good.

    If that fails, use the modified hosts method and manually add any additional domains that the latest lines list may have missed.

    As a last resort, consider temporary workaround method or firewall rules.

    All of these steps are covered in detail in the GenP Wiki, and the guide should be reviewed thoroughly to follow them correctly.

  • source
  • [–] 3 points 1 year ago

    It seems like you've followed the steps in the troubleshooting section. But have you tried using Wintrust on Premiere? Or going to the GENERAL POPUPS EXCEPTION part of the guide and doing the modified config.ini steps, since After Affects can't have Wintrust applied anymore? Also, not sure if its relevant, but your GenP is out of date. The latest one is v3.7.1.

  • source
  • [–] [M] 2 points 1 year ago

    That’s simply because, in the past, there wasn’t a dedicated website available, everything was shared and referenced directly through the guide.

    Now that people can freely access the official website to check for updates themselves, separate release announcements are no longer necessary.

    The guides are always written for and based on the latest available version, so users can easily confirm which version they have by comparing it with the guide.

    Because of that, posting individual release updates would just be redundant at this point.

    As for the changelog entries, those are entirely up to the GenP maintainers who update the website. It’s their choice what to include (or not include) in each release note, just like with the previous v3.6.8 entry: ♪ I know that regression is rarely rewarded; I still need a certain degree of disorder!.

    It’s all written in their usual humorous style, and nothing posted here will influence that.

    That said, I do agree with you, the "More betterer!" line could definitely have been worded better, or at least followed by a short description like: Bugfixes and performance improvements for patching and popup blocking.

    Hopefully, future changelog updates will include a bit more detail again, even if they keep the fun tone we’ve come to expect.

  • source
  • No, Monkrus only distributes his releases via torrents. Any so-called direct download versions found elsewhere are repackaged or leeched copies of his releases. Most of these simply remove Monkrus references and try to pass them off as their own work. You should never use these, as some are known to contain added or modified content, and in certain cases, malicious files. If you choose to download content, always ensure you're using a trustworthy VPN (and optionally a Proxy) to help safeguard your identity and privacy. Although rights holders can actively monitor peer-to-peer networks, the extent of their monitoring depends on various factors, including who they are.

  • source
  • [–] [M] 2 points 1 year ago

    Everything you’ve encountered is already thoroughly explained in GenP Guides, including the Troubleshoot Section and GenP Setup, Troubleshooting, and Best Practices Guide.

    The UPX Error Code 2 simply indicates that the target file was already unpacked, so there was nothing further to unpack.

    The Accept Terms popup you’re seeing is non-AGS-related, it is treated the same way as the Unlicensed popup.

    Premiere Pro: Patch normally, then run WinTrust if non-AGS-related popups (like Accept Terms or Unlicensed) still appear.

    If you prefer not to use WinTrust, or experience issues after using it, untrust the app and use the modified config.ini instead to allow unpacking and patching.

    After Effects: Patch normally, however as clearly stated in the guides, WinTrust should not be run on it, use the modified config.ini instead to allow unpacking and patching.

    If those do not resolve the popups, you’ll need to fallback to alternative methods, such as: using modified hosts file with any additional domains found, temporary workaround method, or firewall rules.

    Keep in mind that modified hosts may not work for every user, and you may not find new domains.

    If that happens, use the temporary workaround method or firewall blocking as a last resort.

    All of these approaches are described in full detail in their respective sections of the guides, review them carefully before proceeding.

  • source
  • [–] [M] 2 points 1 year ago

    This behaviour indicates that the CC app isn’t set up correctly or that its authentication data has become corrupted.

    If everything with the CC app were configured properly, clicking Install would simply start downloading and installing the selected app without any redirects or trial prompts.

    When CC redirects you to Adobe’s website and asks you to start a trial instead of downloading an update, it means the app can’t verify your account’s entitlement.

    If that happens, check CC App Errors in the Troubleshoot Section, use the CC App Uninstaller Tool to repair or completely reinstall the app, then patch it again all as instructed.

    Also, make sure you’re signed in with a free Adobe account and not one associated with an active or expired paid subscription.

    Everything you need to fix this issue is already explained in the guides, it’s worth reading through them before opening new posts about it.

    It would also help if future posts included all the relevant details right from the start, such as the redirect behaviour and the steps you’ve already tried.

    That way, people can better understand the issue and avoid giving general answers that might not apply to your specific situation.

  • source
  • [–] [M] 0 points 1 year ago

    This issue is already covered in the GenP Guides and Troubleshoot Section. If the CC app is showing Trial or Buy instead of Install, it simply needs to be patched with GenP. Most likely, the CC app has auto-updated to the latest version, so you just need to repatch it with GenP. All of this is clearly explained in the GenP Guides.

  • source
  • [–] [M] 1 point 1 year ago*

    There’s no need to reopen or repost about this issue, everything you need is already covered in the Troubleshoot Section.

    You only need to use one of the provided methods; using all of them at once is counterproductive and makes future troubleshooting unnecessarily complicated.

    If you’re using WinTrust, make sure you’ve read and fully understood both sections that explain how it works. That alone should resolve the issue when applied correctly.

    If you prefer not to use WinTrust, then use the modified hosts method instead, ensuring you’ve added the latest lines along with any additional domains identified through the provided third-party method. Alternatively, you can use the temporary workaround method.

    The firewall method should only be used as a last resort, since it completely blocks the app, meaning any online-dependent features will no longer function. All other methods allow the app to remain connected while still removing the popup.

    To summarise: use only one method, follow the instructions in the Troubleshoot Section and the GenP Wiki carefully, and the issue will be resolved.

  • source
  • The simple reason your approach isn’t working is that you are using the wrong method and still expecting it to work.

    You clearly state that you are only using the Remove AGS button. This only works when the popup is AGS-related, that is, the Adobe Genuine Service popup, which explicitly shows Adobe Genuine Service Alert at the top.

    This distinction is clearly explained in the Troubleshoot Section, complete with sample images.

    However, the image you provided shows a popup that is non-AGS-related. It’s simply a variant of the common Unlicensed popup.

    This can be resolved by following the method specific to the popup you’re seeing: Run WinTrust on the app, use modified hosts with any additional domain found, the temporary workaround method, or block the app in your firewall.

    Using the correct method will resolve the issue. Otherwise, you are repeating the common mistake of mismatching non-AGS-related popups with AGS-related solutions and expecting them to work, which they won’t.

  • source
  • Your title is misleading as it suggests the issue is GenP-related, while your actual description shows that Photoshop and Lightroom both load completely and only then crash. That means the problem is not with GenP but with your system or the applications themselves.

    Since this community isn’t Adobe Support, issues like this fall outside our scope; otherwise, posts like these would overrun Lemmy and Revolt with non-GenP troubleshooting. For proper assistance, it’s best to post on the Photoshop or Lightroom Subreddits or check Adobe’s official support forums for similar cases.

    From what you’ve described, where the splash screen appears, the main window opens blank or gray, and then the app closes almost immediately, the behaviour almost always points to a GPU initialisation failure rather than a patching or licensing problem.

    You’re running a laptop with both an Intel integrated GPU and an NVIDIA RTX 3050Ti, and that hybrid setup often causes issues because of how Windows and Adobe apps handle GPU switching.

    Typically, the program launches on the Intel GPU, then tries to switch to the NVIDIA card mid-initialisation, loses its DirectX or OpenGL context, and crashes. Illustrator tends to work fine because it uses the GPU differently and less intensively.

    If this were a GenP or DLL issue, the crash would happen before the main window appears or you’d see an activation error, but here the apps reach the interface stage before closing. That strongly suggests it’s a driver or GPU hand-off problem, not a patch issue.

    The fact that older 2023 versions work also supports this, since they use more forgiving DirectX and OpenGL routines, whereas newer builds rely on stricter GPU handling for AI and compositing features.

    The best approach is to force Photoshop and Lightroom to use your discrete NVIDIA GPU only, either through the NVIDIA Control Panel or in Windows graphics settings. You can also temporarily disable the Intel GPU in Device Manager to test if GPU switching is the cause.

    If the apps stay open, that confirms the problem. Make sure both your Intel and NVIDIA drivers are updated directly from their official websites rather than through Windows Update. If the programs open long enough to change preferences, try disabling GPU acceleration under Preferences.

    In short, this crash pattern is caused by your hybrid GPU configuration or driver setup, not GenP. Fixing GPU switching or disabling hardware acceleration should resolve it, and keeping both drivers up to date will help prevent it from recurring.

    Also, just to clarify your last point: only Premiere Pro and After Effects need to have their DLLs unpacked.

    Photoshop and Lightroom do not require that process, unpacking them is unnecessary and, in fact, not even possible, so that step is irrelevant to the issue you’re describing.

  • source
  • [–] [M] 2 points 1 year ago

    First off, you’re doing something you should never do, mixing and matching GenP and Monkrus methods. Doing so will inevitably cause issues.

    Since you’ve stated that you’re using the GenP method, you should stick with that method only. Monkrus releases are standalone installers that are already prepatched using GenP files and methods. As a result, you’ll encounter the same popup issues regardless of which one you use.

    The popups themselves are not app-specific, they can appear in any Adobe app at any time. These are already thoroughly covered within the Troubleshoot Section, so you should refer there for more detailed information.

    Acrobat cannot have WinTrust run on it, so you’ll need to use one of the alternative methods: Modified hosts file with any additional found domain, temporary workaround method, or firewall rules on the three required files. For all other apps, you can run WinTrust on them, or use the same alternatives above.

    As Adobe has recently made changes affecting certain apps, After Effects and Premiere Pro may not work correctly with WinTrust applied. In such cases, you’ll need to untrust the app and instead use one of the alternative methods mentioned earlier.

    Monkrus installers simply use GenP’s anti-popup patches combined with a manual WinTrust approach.

    All of this information is already explained in detail within the GenP Guides, Troubleshoot Section, GenP Tips/Extra, and Monkrus Tips/Extra. You just need to review those sections and follow the instructions carefully, not everything with GenP or Monkrus is a simple one-click fix.

  • source
  • [–] [M] 1 point 1 year ago*

    You’re seeing the non-AGS-related popup while using a VPN, because your VPN is bypassing your local network rules, such as your hosts file or firewall configurations.

    These rules are what prevent Adobe apps from connecting to certain online services.

    When your VPN redirects traffic through its own DNS or servers, it ignores those local blocks, allowing Adobe to verify licenses and trigger the popup.

    To fix this, you’ll need to adjust your VPN setup rather than disable it entirely. You can try split tunneling, custom DNS, or app exclusions.

    VPNs and Proxies can interfere with how Adobe software communicates locally. Configuration and troubleshooting of VPN or Proxy setups are entirely your own responsibility, support is not provided for issues caused by these tools.

  • source
  • It requires you to be signed in, which is already covered by Monkrus in his own FAQ Section on Fresco torrent tracker.

    Question: Why does the program require authorization immediately after launching?

    Read the FAQ Section for more info...

  • source
  • view more: ‹ prev next ›