This has already been discussed and answered in a previous post here, as well as in several other threads on GenP Revolt and in the Announcements channel.

As for Revolt itself, that’s something you’ll need to sort out on your end. Either Revolt is experiencing delivery issues, your email provider is blocking the messages, or they’re being filtered into your spam/junk folder. Some users have also reported that switching to a different email provider resolved the problem when their main one wasn’t receiving messages.

This is not related to GenP, it’s entirely a Revolt issue. If you’ve already checked everything and still aren’t receiving the authentication email, your next step is to contact Revolt support directly.

There have been no widespread issues with Photoshop v26.10 when repatched with GenP v3.6.8.

For most users, updating and repatching worked fine with no issues.

However, a small number of users have experienced problems, so adjustments were made to address those cases.

If you are encountering issues, updating to GenP v3.6.9 and then restoring and repatching Photoshop should resolve the problem.

Alternatively, you can perform a full uninstall, reinstall, and then repatch using GenP v3.6.9.

Make sure you read the step in full, as your issue is already addressed there.

This error will occur if neither After Effects nor Premiere Pro are installed, since these are the only two apps that are required to be unpacked, no other apps need this step.

If you have the path set correctly and either of the two apps are installed, the app selection window would pop up, allowing you to choose whether to unpack.

If you see the “No file(s) found” message, that means neither After Effects nor Premiere Pro are installed on your system.

No other apps will be listed, so if neither of these two apps exists, GenP will not find anything and move onto the Log tab.

This has already been posted in GenP Lemmy here and is also covered in the GenP Setup, Troubleshooting, and Best Practices Guide, where HEVC use in Premiere Pro is explained in detail.

The issue occurs because GenP modifies Adobe trial versions to function as genuine. The HEVC codec is only available to paying subscribers, which is why it isn’t activated in your case. Simply copying .dll files from older builds will not work either, they only work with the exact same version they were taken from. Newer versions of Premiere change and recompile these files, with updated dependencies and checks, so mismatched .dll files are automatically rejected or fail to load.

Since we are not Adobe Support, assistance with these codec issues is outside our scope. As such posts would overrun Lemmy and Revolt, shifting their focus away from GenP-related discussions.

Yes, everything is the same as before, it just has a new home now.
All the information you need is already included in the provided guides.

The guide lists the 64-bit version of CCXProcess.exe, which is the one actually doing the work.
The other one you mentioned appears under the 32-bit folder because it’s just the older 32-bit launcher stub:
C:\Program Files (x86)\Adobe\Adobe Creative Cloud Experience\CCXProcess.exe

All it does is call the 64-bit version and then exit. It’s only included for compatibility with older 32-bit Adobe applications. Modern systems and current Creative Cloud apps run the 64-bit version exclusively, unless you’re working with legacy software.
So in short: you don’t need to touch the 32-bit entry, just follow the guide as written.

This is simply the common Unlicensed popup, which is non-AGS-related and is clearly covered in the Troubleshoot Section. Taking any AGS-related steps will not resolve this issue, as the popup has nothing to do with AGS.

If you followed the instructions for Premiere Pro and then ran WinTrust as directed, all non-AGS-related popups should already be resolved. If you are still experiencing the issue despite being certain you did everything correctly, then reverting to the modified hosts file is sufficient. Firewall rules are now never required.

As explained in the Troubleshoot Section, this popup is just a variation of the existing non-AGS-related popup. It is not new, nor is it Adobe stepping up.

The issue is simply that you haven’t fully read the GenP Guides, which clearly explain what’s happening in your case. You’ve downloaded the Source version of GenP, which is intended for users who want to compile the app themselves. That’s why it doesn’t include a .exe file, and why it may appear “empty” if you’re expecting a precompiled app.

This is clearly explained in the GenP Guides under the section titled “GenP Distribution Formats Explained”. And it’s also noted on the download tabs of the official GenP website. If you don’t want to build it manually, you should download Binary instead. As it’s precompiled and ready to use right away.

You’re asking where the firewall rule came from, but you’ve also partly answered it yourself.

That rule came from an older version of GenP or a Monkrus release, back when firewall rules were still a standard method for blocking Adobe connections. At the time, using the Popup Blocker option would create an Outbound Windows Defender firewall rule to stop certain endpoints from being reached. This approach was later dropped in favour of hosts file entries, which provided a simpler and more flexible block. From then on, the Popup Blocker button only updated hosts file entries, while some users maintained them manually via third-party tools or by scheduling GenP’s command-line flag.

In current GenP builds, neither firewall rules nor hosts file modifications are required. You can safely remove any remaining Adobe-related entries from both without affecting functionality. The firewall and hosts file options remain in the Pop-up Tools tab, but they’re now intended mainly for users who prefer legacy blocking methods over WinTrust, or for those running older versions that can’t use WinTrust.

However, if you’ve manually used the Firewall Rule option in the Pop-up Tools tab yourself, that could also explain the firewall entry. In current builds, this feature no longer creates a general Adobe firewall rule like the ones used in older versions; instead, it adds separate Outbound rules for each app’s own .exe file, such as Photoshop.exe. This means the kind of single, broad Adobe rule you’re referring to would only come from older GenP versions or from a Monkrus release, not from the current Pop-up Tools firewall option.

If you’ve ever used the Monkrus method, the (prepatched with GenP files and methods) installers also used to add a similar Outbound firewall rule automatically. Since the rule was still on your system, it likely means remnants from older setups hadn’t been cleared until now, something that “Guide #4 – Full Clean” is specifically designed to address.

As for GenP reporting that you’re using a third-party firewall or antivirus when you’re not, that’s due to how it checks your system. GenP queries Windows Management Instrumentation (WMI) for your antivirus status, and WMI can retain stale data from previously installed security software. GenP simply reports whatever WMI returns; if outdated entries exist, that’s what you’ll see instead of your current setup.

This isn’t a fault in GenP, it’s simply how Microsoft stores and reports that information. Even users who have only ever run Windows Defender can encounter this if WMI retains old security software records. In your case, if WMI lists only Defender yet GenP still flagged something else, the query result was inaccurate. Sometimes users later recall having another antivirus or firewall installed in the past, but even if that’s not the case, WMI can still occasionally misreport, and GenP can only display the data it receives from your system’s own WMI.

That is just the common Unlicensed popup, which is non-AGS-related.

This is already covered in the Troubleshoot Section within GenP Guides, refer to the method listed there.

For most users, simply unpacking (where required) and patching is enough to resolve it.

However, for some, using WinTrust is necessary to remove any remaining non-AGS-related popups.

If you decide to use WinTrust, make sure you read about it thoroughly first so you fully understand how it works.

Follow the instructions in the Troubleshoot Section for this popup, and you should be able to resolve it without issue.

Otherwise, Revolt is working perfectly fine, if it isn’t loading for you:

• Try another web browser.
• Temporarily disable any adblockers or privacy extensions.
• Switch from Wi-Fi to wired (or vice versa) to rule out router or signal issues.
• Use a VPN to bypass possible ISP or regional restrictions.

This is not a GenP-related issue; it’s a problem with your system configuration.

The two most common causes of error 0xc0000142 in After Effects are a lack of Advanced Vector Extensions 2 (AVX2) support in your CPU, or missing or damaged Microsoft Visual C++ Redistributables. AVX2 is now required for many newer Adobe apps, so if your processor does not support it, the only solution is to install an older version of After Effects that is compatible with your hardware.

If the older version is not available through the standard Adobe rollback method, follow Guide #4: Full Clean to completely remove all existing Adobe installations using the GenP process. After that, perform a clean installation of the older version using the Monkrus method. It is important never to mix or match GenP and Monkrus versions, or run GenP on Monkrus.

If the problem is not related to AVX2 or Visual C++ Redistributables, it may be caused by corrupted Windows system files, outdated or incompatible GPU drivers, outdated DirectX runtimes, conflicts with background software such as antivirus tools or overlays, improper file or folder permissions, DLLs blocked or quarantined by Windows security, residual files from a faulty Adobe installation, or damaged user preferences and cache within After Effects. In rarer cases, it can also be caused by a corrupt Windows user profile or instability from CPU or RAM overclocking.

Since we are not an extension of Adobe Support, we do not provide assistance for these types of issues, as such posts would overrun Lemmy and Revolt, shifting their focus away from GenP-related discussions. As outlined in the GenP Guides and the GenP Setup, Troubleshooting, and Best Practices Guide, these issues fall outside our scope. For further help on this, post on the After Effects Subreddit, or search the Adobe Community where this error has been discussed extensively.

You’ve missed one key step that’s in the guides: every time CC gets updated, you need to repatch it with GenP.

When CC itself is updated, make sure to allow the update to complete (even if the “Automatically keep Creative Cloud up to date” option is toggled off).

Once the update finishes, run GenP again to repatch the CC app. If you try to patch it before the update is complete, it might self-repair and undo the patching.

So, after updating the CC app, use the “Search” and “Patch” options in GenP, and that should fix the issue.

Also, if you see the “TRIAL/BUY” instead of “INSTALL”, that’s a strong indicator that the app has likely been updated and needs to be repatched.

This is especially true if you haven’t used the app in a while and it’s been updated to the latest version, as shown in the Compatibility List.

Remember, updates to the CC app are mandatory for compatibility, and blocking Adobe Desktop Service in the firewall might not always work as expected.

If you run into any issues along the way, you can quickly fix them by using the Repair option in the CC App Uninstaller Tool, which is mentioned in the “CC App Errors” section of the Troubleshoot Section.

The guides cover all these steps in more detail, so you might want to go over them again if you haven’t already.

To clarify, you haven’t mentioned which method you’re using, GenP or Monkrus.

Both methods work fine with Enhance Speech or Transcribe, and both support additional language packs.

Here’s how each method works:

GenP:

• If you’re using the GenP method for Premiere Pro, it functions just like the official Adobe version.

• Download any additional language packs directly through Premiere Pro or via the CC app under Premiere Pro Add-ons.

• You no longer need to worry about hosts or firewall settings when using the latest GenP v3.6.8.

• Just ensure that you’ve unpacked the app before patching, and if needed, use WinTrust to avoid any non-AGS-related popups.

Monkrus:

• On the other hand, Monkrus repackages Premiere Pro to keep the initial standalone installer smaller.

• An additional Speech Pack needs to be downloaded separately and installed over your existing Premiere Pro installation.

• However, Monkrus also now includes a manual WinTrust option for you to use as well (just like GenP has for a good while now), instead of just relying on the GenP anti-popup patches only.

• Meaning you no longer need to mess with firewall or host file modifications.

Additional Help:

If you’ve missed it, this topic is covered in more detail under “Enabling Speech to Text and Language Packs in Premiere Pro” in both the GenP Setup, Troubleshooting, and Best Practices Guide and the Monkrus Setup, Troubleshooting, and Best Practices Guide.

If you’d refer to these, you’ll find a more in-depth explanation.

Everything you need is already in the pinned posts at the top of our Lemmy instance.

Recommended reading includes the GenP Wiki and GenP Guides / Downloads.

Then, depending on the method you choose, refer to either the GenP Setup, Troubleshooting, and Best Practices Guide or the Monkrus Setup, Troubleshooting, and Best Practices Guide, for additional info.

Make sure to read our Rules and Disclaimer, and the Friendly Reminder as well, as they are equally important!

Take your time going through the guides to understand how GenP works.

If you run into any issues, feel free to post back here or on Revolt.

Also, take a moment to browse older posts on Lemmy or Revolt before creating a new one.

You’ll likely find that your question has already been discussed.

People often repost the same or similar questions, so searching first helps keep the community tidy and efficient.

If Lightroom doesn’t show up under “Installed Apps” in CC and you’re unable to update it.

But it is available for a new install, this likely indicates that the app wasn’t installed or patched properly.

As per the GenP method, no apps should show as “Trial” or “Buy”, they should all show as “Install” if CC is properly patched.

If Lightroom or Lightroom Classic is not showing as an update but available as a new install.

You should be able to simply install the latest version or use the “Other versions” list to install an older version instead.

If you’re using the GenP method, both Lightroom and Lightroom Classic should appear in the Apps tab of CC.

The only reason they may not show up is if your device is incompatible with the latest (or even previous) releases of the apps.

If that’s not the case, try signing out of CC, restarting your device, and then signing back in.

This can sometimes resolve issues with app visibility.

Additionally, ensure that your device meets the system requirements for the version of Lightroom you’re trying to install or update.

There are also other potential causes.

A corrupted CC installation might prevent apps from showing up or being properly managed.

If that’s the case, try reinstalling CC using the CC App Uninstaller Tool to remove it first.

If you have multiple Adobe accounts, make sure you’re signed in with the correct one.

As sometimes apps won’t appear if you’re logged into an account that isn’t linked to the right subscription.

However, with GenP (and Monkrus) method, you should only be using it as non-genuine, never mix genuine with non-genuine, which includes the apps and the account used as well, therefore all apps should be readily available for you.

It’s also worth checking that you’re using the latest version of CC; an outdated version may not recognise newer apps like Lightroom.

Network or server issues can sometimes interfere as well, so check Adobe’s support page for any known outages or problems.

Lastly, if you’re on a restricted user account, you may not have the necessary permissions, so try running CC as Administrator.

Note that GenP does not support Lightroom itself, only Lightroom Classic.

While you can install and patch Lightroom, some users have issues with it because it is cloud-based, whereas Lightroom Classic is fully desktop-based and fully supported.

Finally, please keep in mind that if everything has been installed and patched properly, this issue is likely not related to GenP.

It is more likely to be an in-app or system-related issue.

Since we are not an extension of Adobe Support, we do not provide assistance for these types of issues.

Otherwise, such posts would overrun Lemmy and Revolt, shifting their focus away from GenP-related discussions.

If you need more help on this, do as instructed in GenP Guides and GenP Setup, Troubleshooting, and Best Practices Guide.

Post on the Lightroom Subreddit or search the Adobe Community for similar discussions.

There is nothing in the Troubleshoot Section specifically for this issue, as it’s not a problematic popup.

What you’re seeing is just the CC app prompting you to update to the latest version (v6.7.0.278).

This is completely normal and expected, even if you have “Automatically keep Creative Cloud up to date” toggled off in your CC app preferences, as instructed.

Adobe enforces these updates because the CC app acts as the central hub for managing all your individual apps, which is why the updates are listed as mandatory in the CC app release notes.

Since the individual apps receive regular updates (at least once a month for most), the CC app itself must stay current to maintain compatibility and functionality.

To resolve this, simply update the CC app and then repatch it with GenP. It’s completely fine to do so.

You can refer to the Compatibility List for the latest supported versions, including for the CC app.

CC app and individual app updates are covered in both GenP Guides and GenP Setup, Troubleshooting, and Best Practices Guide, though not specifically the popup image itself.

As for the 6-digit code popup, that was Adobe requesting you authenticate your email for the free Adobe account setup.

This is a step Adobe prompts you for if it wasn’t completed earlier, as most people will do it when they first set up the account.

Once authenticated, Adobe won’t bother you with this popup anymore.

Lastly, if you’re using GenP v3.6.8 and have applied WinTrust on all the installed individual apps, you no longer need to worry about modifying the hosts file or adjusting firewall settings.

The patching process, including any required unpacking where necessary, will remove non-AGS-related popups for most users.

With the addition of using WinTrust, this will remove non-AGS-related popups for all, rendering hosts or firewall modifications redundant, as they’re no longer needed.

The AGS-related popup might still appear; however, that is easily removed using the provided method for it.

You’ve just downloaded Source, which requires you to build it yourself before you can use it.

This is clearly explained in the GenP Guides under the section titled “GenP Distribution Formats Explained”, and it’s also stated on the download tabs of the GenP website.

If you don’t want to build it manually, then you should download Binary instead, which is already precompiled and ready to use.

Nothing has changed regarding GenP, it still does not support ARM architecture. GenP is only compatible with Windows 10 and 11 on standard x64-based systems and does not work on modified versions of Windows or on devices using ARM processors.

The Surface Pro 11 uses a Snapdragon X-series CPU, which is based on ARM architecture. While Windows 11 for ARM includes an emulation layer that allows some x86 and x64 apps to run, particularly those that are not able, or not yet able, to run natively, this does not guarantee compatibility with all software, especially low-level tools like GenP.

Regarding your claim of having run Photoshop 2024 and GenP previously on the same device: that was likely possible because Photoshop 2024 still included an x64 version, which could run under emulation. GenP may have worked with that emulated version at the time. However, with Photoshop 2025 (v26.x), Adobe are shifting more fully to native ARM64 builds on ARM hardware. These native versions bypass emulation and are therefore incompatible with GenP, which only supports patching x64 binaries.

Emulated apps can also break due to Windows updates, driver changes, or app updates, especially when tools rely on precise system-level behaviour, like GenP does.

Ultimately, this issue is not GenP-specific but rather a limitation of running Windows on ARM-based hardware. If you’re looking for more information or need help troubleshooting Photoshop itself, you’re better off posting on the Photoshop Subreddit or searching the Adobe Community, where similar ARM-related discussions already exist.

Note too that even if you try using releases from Monkrus, you’ll encounter the same issue. These builds are simply prepatched using GenP files and methods, so they are subject to the same architectural limitations. Until GenP officially supports ARM architecture, Monkrus won’t either, nor will any third-party software sources that merely repackage or redistribute the same underlying tools.

This issue is already addressed in the Troubleshoot Section of the GenP Guides. Under the heading “CC App Errors”, you will find all the relevant information to resolve this problem.