Mean_Plantain_7909 @ Mean_Plantain_7909 @lemmy.dbzer0.com

wiki-user: Mean_Plantain_7909

---

Read more

Posts

7

Comments

44

Joined

4 mo. ago

Moderating

---

Start by ensuring you are following GenP Guides and read the Troubleshoot Section.

For most users, simply patching (including the required unpack for Premiere Pro beforehand) removes all non-AGS-related pop-ups.

In such cases, you shouldn’t need modified hosts or firewall settings either.

For some users, simply patching doesn’t always work, in such cases, you can make use of WinTrust for the specific app.

By trusting the required app and restarting, the change should eliminate any non-AGS-related pop-ups.

Simply repatching multiple times won’t help either, especially with Premiere Pro, as it needs to be unpacked before patching to work properly.

Also, patching only works once; repatching after the initial patch won’t overwrite the existing one.

When you’ve patched correctly or used WinTrust, GenP should have removed all non-AGS-related popups, and you can run Premiere Pro without the need for modifying hosts or using a firewall.

If the issue still persists, you can revert back to the previous methods of modified hosts or firewall rules, though they should no longer be necessary.

You may still encounter AGS-related pop-ups, like the Adobe Genuine Service popup, although this is easily removed via another method, as mentioned in Troubleshoot Section.

This used to be a common issue discussed on the GenP subreddit. The Remove Tool in Photoshop never actually used Generative AI credits, it operates independently.

For most users, the tool has been working fine. The main change that started last year was that, for some users, Photoshop began requiring an active internet connection for certain features to function properly, which included the Remove Tool.

Previously, many users would patch Photoshop, block it via the hosts file, and add a firewall rule for the app, this setup worked without issue for a while. However, Adobe later updated the software to require an internet connection, which caused problems with that configuration.

As GenP eventually switched to using only patch and hosts file (dropping the firewall requirement), the solution was simply to remove the firewall rule and allow Photoshop access to the internet. After doing so, the Remove Tool began working again.

Currently, Photoshop v26.8 patched with GenP v3.6.7 works without any major issues, and there's no longer a need to modify the hosts file or add a firewall rule. Some users might still need to apply WinTrust, but overall, it runs smoothly for most people.

Just to clarify: The Remove Tool (introduced in Photoshop 2023) is part of the non-generative AI features, it’s based on Adobe’s internal content-aware technology, not on Firefly or cloud-based generative models that consume AI credits.

While it doesn’t require Generative AI credits, it can still depend on an internet connection in some cases (especially with cracked or modified versions), as Adobe may validate license status or related functionality online.

Blocking Photoshop through the firewall can cause the tool to stop working.

Before posting, please scroll through previous posts on GenP Revolt as this issue has been addressed before, with images showing the same error you're experiencing, like here and here. The replies posted there would have given you the answer without needing to post again.

Two things you can do, as mentioned previously:

Ensure you are not using an outdated version of GenP and are always using the latest release, as there was an issue with older versions of GenP with Acrobat, but unless you’re still using an earlier version, this shouldn't be an issue now. Ensure Acrobat is properly installed and that your antivirus hasn’t blocked or quarantined the file after patching.

If the issue persists, use the Acrobat Cleaner Tool from here to completely uninstall Acrobat. Then, reinstall and repatch with GenP v3.6.6. After patching, open Acrobat to see if the error occurs again. If it does, it's likely due to your antivirus blocking or quarantining the modified file created during patching. Check your antivirus quarantine folder and remove the file if found. Alternatively, simply exclude Acrobat from antivirus scanning, and it should work fine. Avoid using the Windows repair option, as it may not clear everything. If it isn't the antivirus causing the issue, using the repair function might not resolve the underlying problem.

This is already covered in the Troubleshoot Section of the GenP Guides.

To begin with, GenP is never installed; you install Adobe software. GenP is a patcher and, therefore, will only patch files that are already installed.

If you've followed all the steps in the GenP Guides properly and completely, including any required unpacking beforehand, there should be no issues with patching CC or individual apps using GenP v3.6.6.

However, if you're unable to find the folder C:\Program Files (x86)\Common Files\Adobe\Adobe Desktop Common, it suggests that the installation may not have been completed correctly. This could be due to a missed step, an incorrectly configured setting, or simply that the CC app has not been installed at all. Please double-check the guide to ensure everything was done exactly as instructed.

If you're using ARM architecture or an unsupported OS, GenP will not function as intended. Additionally, verify that your antivirus or admin permissions are not blocking the process.

If all steps are followed correctly and the CC app is installed, there should be no issues.

Yes, H.265 works with the latest Premiere Pro v25.2.3 patched with GenP v3.6.6. However, some users have previously reported in older GenP posts on Subreddit and Discord that HEVC compatibility breaks after upgrading from previous versions, so results may vary depending on your setup.

If Premiere Pro states that the codec is missing, ensure you have the latest HEVC Video Extensions installed from the Microsoft Store. While some users have successfully enabled HEVC using third-party codec packs, Adobe officially recommends sticking with the Microsoft version for better compatibility.

If your current setup works fine, you might consider staying on your existing version. However, if you want to upgrade, you can try updating to v25.2.3 and test HEVC functionality. If it doesn't work, you can rollback to your previous install and repatch with GenP to restore your setup.

If you still experience issues with HEVC after upgrading, converting HEVC files to a more compatible format like ProRes using HandBrake, Shutter Encoder, or Adobe Media Encoder could be a practical workaround.

Additionally, checking Adobe Community Forums and the two Premiere Pro Subreddits might provide insights into what has worked for other users. Clearing Premiere’s media cache could also resolve potential import issues, and enabling hardware-accelerated decoding in the Media tab under Preferences might improve performance when working with HEVC files.

Also, consider using DaVinci Resolve as an alternative, or even learning both Premiere Pro and DaVinci Resolve to integrate them into your workflow for maximum flexibility. Many professionals use both for different aspects of their projects, combining the strengths of each software to achieve the best results.

However, hardware decoding for HEVC is only available in DaVinci Resolve Studio, meaning playback and editing performance may be slower in the free version. Additionally, some users have reported that 10-bit HEVC files (especially 4:2:2) may not work properly in the free version, while 8-bit HEVC (4:2:0) might still be usable depending on system codecs. If playback is slow or files appear as "Media Offline," converting HEVC to ProRes or DNxHR using HandBrake or Shutter Encoder can be an effective workaround.

This is already covered in Announcements on Revolt.

You can't have looked that hard then.... GenP Guides / Downloads

This issue is not related to GenP but rather an in-app problem. 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.

As outlined in the GenP Guides and the GenP Setup, Troubleshooting, and Best Practices Guide, these issues fall outside our scope.

Given your post, this is not caused by GenP. It is most likely due to your usage of third-party plugins, as After Effects can be finicky when it comes to unofficial plugins, especially if they aren’t fully optimised for the latest version.

Third-party plugins can cause UI issues in After Effects due to compatibility conflicts, interference with other plugins, or reliance on GPU acceleration that may not work correctly with certain hardware.

Some plugins require significant system resources, leading to performance issues, while others may break after an After Effects update if they rely on outdated code or unsupported APIs. If you're experiencing glitches, disabling plugins individually or running After Effects in Safe Mode can help pinpoint the cause.

Users have reported similar UI glitches when scrolling, particularly when using certain GPU settings or incompatible plugins, as like here, here, and here. Visual glitches have been known to be caused by plugins like Red Giant VFX Shadow & Primatte, as already posted in Adobe Community here.

Try doing this first:

• Ensure You’re Using a New Free Adobe Account: Do not use the same account that had an existing subscription or any free trials linked to it.
• Disable Plugins: Try running After Effects without third-party plugins to see if the issue persists.
• Run After Effects in Safe Mode: Launch After Effects in Safe Mode to limit potential conflicts and test for stability.
• Update GPU Drivers: Some UI glitches can be caused by outdated or incompatible GPU drivers.
• Turn Off Hardware Acceleration: Go Preferences > Import and disable hardware-accelerated decoding.
• Check Known Issues: Adobe has a list of known After Effects issues that might be relevant.
• Reinstall After Effects: If all else fails, a clean reinstall might help.

Otherwise, it is something else in After Effects or your own device that is affecting you.

Additional steps:

• Check System Requirements: Ensure your hardware meets After Effects recommended specifications, especially your GPU and RAM.
• Used Device: Check your own device's setup compared to Adobe's own "Hardware recommendations for Premiere Pro and After Effects" here.
• Adjust Display Settings: Lowering your display resolution or refresh rate might help stabilise UI rendering.
• Disable GPU Acceleration: In Preferences > Display, try disabling GPU acceleration to see if it resolves the glitch.
• Purge Cache & Memory: Go Edit > Purge > All Memory & Disk Cache to clear any corrupted temporary files.
• Test in a New User Profile: If possible, create a new user profile on your computer and test After Effects there to rule out system-wide issues.
• Check for Software Conflicts: Close any background applications that might interfere with After Effects, such as screen recording software or overlays.
• Try a Different Version: If the issue started after an update, rolling back to a previous version of After Effects might help.

Additionally, if you have patched the CC app and individual apps using GenP v3.6.4, including any necessary unpacking of Premiere Pro or After Effects beforehand, then there should be no need to use either a hosts file or a firewall. For any patching issues, simply use WinTrust for the specific app instead.

This issue is not related to GenP but rather an in-app problem. 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.

As outlined in the GenP Guides and the GenP Setup, Troubleshooting, and Best Practices Guide, these issues fall outside our scope.

If you’ve already tried basic fixes, try running through these options to help resolve the issue.

Fixing Creative Cloud Installer Crashes (Exception Code 0xc0000096)

The exception code 0xc0000096 typically indicates a "privileged instruction" or "invalid opcode" error, meaning the installer is attempting to execute instructions that your system doesn’t allow. This can be caused by corrupted system files, virtualisation conflicts, incompatible hardware, or interference from third-party software.

Step-by-Step Fixes to Try

1. Repair System Files

Corrupted system components are a common cause of installer failures. To repair them:

1. Open Command Prompt as Administrator
2. Run:

       
   sfc /scannow
   
     

3. If issues persist, run:

       
   DISM /Online /Cleanup-Image /RestoreHealth
   
     

4. Restart your PC and retry installing Creative Cloud.

2. Use the Adobe Creative Cloud Cleaner Tool

Even after manual removal, leftover Adobe registry entries and files can interfere.

• Download the Adobe Creative Cloud Cleaner Tool
• Run the tool as Administrator
• Select "All Adobe Products" for a full cleanup
• Restart your PC before reinstalling

3. Check Windows Compatibility Settings

Incompatibilities between the installer and your Windows version can cause crashes.

• Right-click the installer → Properties → Compatibility tab
• Check “Run this program in compatibility mode for:” and select Windows 8 (or an earlier version)
• Apply and run the installer

Also ensure your system is fully updated:

• Settings → Update & Security → Windows Update
• Install all available updates and restart your PC

4. Install Required System Dependencies

Adobe software depends on system libraries that may be missing or outdated.

• Install the latest Visual C++ Redistributables (install both x86 and x64)
• Ensure the latest version of the .NET Framework is installed

5. Try an Offline Installer

Some users have better results using an offline installer instead of the web-based one.

• Offline installers may be available via the Adobe Enterprise Portal or by request from Adobe Support
• Contact Adobe to request one if needed

6. Perform a Clean Boot

Third-party apps or services can interfere with installers.

1. Press Windows + R, type msconfig, press Enter
2. Go to the Services tab → Check "Hide all Microsoft services" → Click Disable all
3. Open Task Manager → Disable all Startup items
4. Reboot your PC and try the installer again

7. Verify Virtualisation or CPU Issues

If you're using a virtual machine or emulation environment (QEMU, Wine, Sandbox), certain instructions may not be supported.

• Run the installer on real hardware, not a VM
• If using a VM:
  • Enable AVX, SSE4.2, or VT-x in virtualisation settings
  • Optionally, disable Hyper-V via OptionalFeatures.exe
• If possible, test on a different physical system

8. Check Disk and User Profile Integrity

Corrupted disks or profiles can cause installer issues.

• Open Command Prompt and run:

      
  chkdsk /f /r
  
    

• Verify full access to the following folders:

      
  C:\Program Files\
  C:\ProgramData\
  C:\Users\[YourName]\AppData\Local\Temp\
  
    

• Create a new local Administrator profile and try the installation there

9. Analyse Crash Dump (.dmp) Files

If the installer generates .dmp files, they may reveal the cause.

• Use WinDbg from the Windows SDK
• Load the .dmp file and run:

      
  .exr -1
  
    

• If you’re unsure how to analyse the file, you can upload it to Adobe Support for help

Additional Fixes

• Boot into Safe Mode with Networking, then retry the installation:
  (Shift + Restart → Troubleshoot → Advanced Options → Startup Settings → Press 5)
• Use Sysinternals Autoruns to identify potentially conflicting drivers or DLL hooks
• Temporarily disable or uninstall tools known to hook into system processes (e.g., legacy antivirus, overlays, system monitors)

Last Resort Options

If none of the above works:

• Test the installer on a clean Windows install (separate partition or temporary installation)
• Perform a Windows in-place upgrade repair using a Windows 10/11 ISO

Contacting Adobe

If the issue persists, contact Adobe Support and provide:

• The crash .dmp file(s)
• Your setup.log (found in %temp%)
• A screenshot or detailed description of the error

Or check Adobe Community for similar posts, such as
Creative Cloud Installer Crashes.

They may be able to offer a targeted solution based on your system trace.

Final Reminder

Before making significant system changes, always back up your data. Consider creating a system restore point or a full backup to protect your system.

Summary Checklist

• Run SFC and DISM to repair system files
• Use Adobe's Cleaner Tool to fully remove residual data
• Ensure Windows is fully updated
• Install both x86 and x64 Visual C++ Redistributables
• Perform a clean boot to eliminate conflicts
• Try compatibility mode and Safe Mode
• Analyse or share crash dump files if needed
• Request an offline installer from Adobe
• Contact Adobe Support with full error logs

Ensure that you are not mixing up the two Adobe apps.

CC App Uninstaller Tool:

Use this to repair, uninstall, or reinstall the CC app itself.

Creative Cloud Cleaner Tool:

Use this to uninstall individual or all apps. However, it can leave remnants behind, so tools like Revo are a better option for complete removal.

Important Note:

Both the CC App Uninstaller Tool and the Creative Cloud Cleaner Tool can return a "Completed with errors" message. This typically happens when certain files or registry entries fail to be removed during the uninstallation process. If you encounter this error, rerunning the tool may help clear any remaining components. Additionally, manually deleting leftover Adobe folders or using third-party uninstallers like Revo Uninstaller can ensure a more thorough removal.

Everything is running smoothly. The Advanced task was already modified to resolve previous issues. To fix it, simply rerun the Advanced task script in PowerShell as Admin, it will overwrite the existing .ps1 file and scheduled task. If you encounter any issues now, they are likely caused by your device's network or your ISP blocking access.

Since we are not Adobe Support, you can find answers directly from official resources.

What is a .prin file? and Media intelligence and Search panel FAQs

.prin files are part of Adobe's Media Intelligence feature. They act as index files, storing visual analysis data for all video clips in a project, enabling easier searches via Adobe's AI-powered Search Panel.

How to Disable Media Intelligence Indexing in Premiere Pro

• Export Screen: Toggle off the indexing option in the right-hand menu.
• Preferences: Go to Preferences > Media Intelligence and disable indexing.
• Clear Media Cache: This may help prevent .prin files from reappearing.

This issue may be related to GenP, but it is more likely an in-app problem. 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.

Premiere Pro & GenP

If you're using Premiere Pro, ensure that you have GenP v3.6.4 and have properly unpacked both Premiere Pro and After Effects before patching, as instructed in the GenP Guides. If done correctly, you should not experience issues with either app.

Error Code 87 Explained

• Installation Issue: Adobe’s support page lists Error 87 as “Another installer is already running,” meaning an active process is preventing installation.
• WinHTTP Error: “Failed to open WinHTTP Session. The parameter is incorrect (Error code 87)” suggests a secure connection issue, possibly due to misconfigured SSL/TLS settings or network protocols.

If both errors occur, Adobe apps may be struggling with installation conflicts and authentication errors.

Fixes for WinHTTP Errors (87, 12018)

1. Reset WinHTTP: Run netsh winhttp reset proxy in an Administrator Command Prompt.
2. Enable TLS 1.2/1.3: Navigate to Internet Options > Advanced and verify these settings.
3. Check Network & Proxy Settings: Disable VPNs/proxies and ensure Adobe servers are reachable.
4. Test Connection: Run Invoke-WebRequest -Uri https://adobe.com/ in PowerShell.
5. Update/Reinstall Adobe: Ensure Adobe apps are up to date or reinstall if needed.

If the issue persists, consider checking Adobe forums, the Adobe Community, or the app’s own Subreddits for known issues.

Log Files in Adobe Apps

While using Premiere Pro, other Adobe apps like Illustrator, After Effects, or Photoshop may generate log files in their respective project directories. If this issue occurs across multiple apps, it might be due to a recent update affecting log storage behaviour.

Adobe:

Additionally, Gudetama log files have been a known issue in Illustrator and possibly other apps. Users reported these logs being generated each time they open or save a file, particularly after updates.

GenP Fix:

Some users have worked around this issue by commenting out the "Good1" pattern/patch in the config.ini file and ensuring they ran WinTrust on the specific app to cover the modification. If you're unsure about doing this, and the log files aren't interfering with app performance, it's safe to simply ignore them and continue using the apps normally.

Adobe’s Suggested Fixes

• Adobe acknowledged and patched this issue in 2022, requiring users to update to v27.3.1.
• Otherwise, you can disable Automatic Proxy Detection:

1. Go to Control Panel > Internet Options > Connections > LAN Settings and uncheck “Automatically detect settings”.
2. Go to Windows Settings > Network & Internet > Proxy and turn off “Automatically detect settings”.

For more details, check out discussions on the Adobe Community here or here.

If all else fails, you can roll back to a previous version of the app. If the issue started after an update, reverting to the previous version may resolve it.

Final Thoughts:

While this problem can be GenP-related, it is more likely to be an in-app issue, often linked to recent updates or changes in configuration settings in Adobe software. If the log files are not causing performance issues or affecting your app's functionality, there’s no need to worry. For more specialized troubleshooting related to Adobe apps, referring to Adobe support, their forums, or the app’s Subreddits may provide more tailored solutions.

Adding Here For People Reading Later On:

What Are Gude Logs?

These logs are internal diagnostics generated by Adobe apps (like Illustrator, Premiere Pro, After Effects, etc.)

When they attempt to perform network-related tasks, such as license checks, telemetry, or secure connections.

The errors you’re seeing:

[CRITICAL] SharedConnection - Failed to open WinHTTP Session. The parameter is incorrect. [ERROR] Failed to Configure Secure Protocols. WinHTTP Incorrect Handle Type.

…are typically triggered when the app is blocked from reaching Adobe's servers (e.g., due to patching, firewall rules, or proxy settings).

Do They Affect Performance?

In most cases, no. These logs:

Don’t interfere with saving, exporting, rendering, or editing.

Don’t crash the app or cause instability.

Are not visible to clients or embedded in project files.

They're just background reports of failed network attempts, and unless you're relying on Adobe cloud features (like syncing, fonts, or team collaboration), they’re irrelevant.

When to Worry

You only need to investigate further if:

The app fails to launch or crashes unexpectedly.

You’re unable to save or export files.

You rely on Adobe cloud services and they’re not working.

Otherwise, you can safely ignore or delete the logs.

Final Note:

Because these apps are being used through non-genuine methods, it’s possible that both GenP and Adobe are contributing to the issue. In many cases, these logs and errors simply occur because Adobe can’t "call home" to verify licenses or sync cloud features. This doesn’t usually affect core functionality, but it can trigger background errors like the ones described above.

Did you read Compatibility List before posting or not?