The new v 27.7.0 Remove Tool "On Device" feature requires component download, but the latter always fails

​@Sere.Citiverse you’re not alone

System:

• Device: ASUS ROG Zephyrus Duo 15 SE (GX551QS)
• CPU: AMD Ryzen 9 5900HX
• RAM: 32GB (12GB+ free during installation)
• OS: Windows 11 Home x64 (Build 26200)
• Photoshop Beta version: 27.7.0.3511
• Adobe installer process: 32-bit

Steps to reproduce:

1. Open Creative Cloud Desktop
2. Navigate to Photoshop Beta → Get Add-ons → Remove tools advanced components 
3. Installation reaches ~49-62% and fails with Exit Code 127
4. Error repeats identically on every attempt regardless of system state

What was tried without success:

• Multiple clean installs of Photoshop Beta and Creative Cloud using Adobe CC Cleaner Tool
• Cleared C:\adobeTemp before each attempt
• Ran Creative Cloud as Administrator
• Increased Windows Virtual Memory (page file) manually
• Set full permissions on all Adobe temp folders
• Disabled all background Adobe processes before installation
• Attempted installation from both Photoshop Beta and standard Photoshop
• An Adobe remote support agent accessed the system and modified AppData folder permissions without resolving the issue

Possible root cause identified from logs: The Adobe installer runs as a 32-bit process. A 32-bit process has a maximum virtual address space of 2GB. After Windows reserves space for kernel, DLLs, and heap, there is no contiguous block of ~1.07GB available — regardless of how much physical RAM is free. This is a design issue in the installer: extracting files of this size requires either chunked extraction or a 64-bit installer process.

Exact error from Summary.htm log (repeats 92 times per attempt):

Failed to allocate buffer for file C:\adobeTemp\ETRxxxx.tmp\34\UltraCafModels\Nano_data_1\unet_128_128_dmd\30983be4-95a8-11f0-8993-b69f465218a5.data.00 of size 1121067432
Failed memory allocation after sleep also
Extraction failed with returnCode=-1

All 4 packages fail identically: Nano_data_1 through Nano_data_4, each requiring a 1,121,067,432 byte contiguous buffer.

Additional finding: By reading the .pimx manifest files extracted from the packages, the correct installation destination was identified as: C:\Users\[user]\AppData\Roaming\Adobe\Adobe Photoshop (Beta)\AddOnModules\sensei_model_cache\inpainting_ai\ultra_caf\

Files were manually extracted using 7-Zip and placed in the correct location, but Photoshop Beta does not recognize manually placed files and continues attempting reinstallation — suggesting the installer also needs to write a completion record that it cannot reach due to the extraction failure.

Request:

1. HELP!

Same issue.

RTX 5090

i9-14900K

64 GB ram

running adobe on a NVMe WD blue sn5000 1tb with 400+gb free space

Had the download fail at 48%, 60% and 92%, seems to fail at 48% the most. Current internet speed is Download Mbps

517.64, Upload Mbps 70.59.

Photoshop Beta v27.9 failed at 64%, 68% and 82%

Error code: 127

the previous thread regarding the Advanced Remove Tool Component has now dissapeared and the link goes 404.

installation error code while trying to download/install Advanced remove Tool Components:

Error Code: 127 

Same issue here:
NVIDIA GeForce RTX 4070 Ti SUPER
16061 MB VRAM detected by Photoshop
Photoshop reports insufficient VRAM for on-device Remove Tool processing
GPU Compatibility test passes

I just spend around 2 hours with an Adobe Remote Support technician Mohammed and we tried everything under the sun to try and resolve this issue, to no avail.  The issue persists.  Error Code: 127

the technician said they will follow up with me via email when/if he hears back from his backend team regarding this issue.

Getting the same error - June 20th 2026 on both Photoshop Bets (27.9) and Photoshop 2026 (27.8)

Tried add-on download through both CC Application and directly on Photoshop app. Fails everytime after about 20mins {or ~ 60%) of downloading Ai model contents from Adobe servers.

Error code: 127.

AMD 9950x3d

64GB RAM ddr5

Nvidia RTX 4090  - 24GB VRAM

GPU Driver:   610.47

Hi ​@Francesco277711048b98,

Thanks for sharing the details. Error 127 generally indicates that the installer is unable to extract or write files during installation.

I can see you’ve already tried many of the common fixes, so let’s try to narrow this down further.

A few questions:

• Are you the administrator of this machine?
• Is this a personal PC or a company-managed device?
• Do you have any antivirus, endpoint protection, or security software installed (Bitdefender, ESET, CrowdStrike, SentinelOne, Defender for Business, etc.)?
• Does the same error occur on a different internet connection (for example, a mobile hotspot)?

One thing I’d like you to test before going deeper is to create a na brand-new local administrator account and test the installation there before running additional cleanup on your main profile:

https://support.microsoft.com/en-us/windows/manage-user-accounts-in-windows-104dc19f-6430-4b49-6a2b-e4dbd1dcdf32

This helps us determine whether the problem is specific to your current Windows profile.

In that case, we can look at a deeper cleanup of the existing profile.

Also, although you’ve already worked with the AdobeTemp folder, could you confirm:

• Does C:\adobeTemp currently exist?
• Do both SYSTEM and Administrators have Full Control permissions on that folder?

The new admin-account test is the most valuable next step here because it quickly tells us whether we’re dealing with a profile-specific issue or something broader.

Best,
Anshul Saini

This is apparently a work in progress. With an RTX5060 Ti 16GB I should be ready for business.

• At first the advanced components didn’t want to install.
• Then later they did install, but the “Device” option was still grayed out and unavailable.
• Now, after the 27.8 update, it has become active and available - but when I click it, I get a notification that my GPU isn’t supported.

So we’re getting there, slowly 😊

Not a big deal for me, it’s not something I want to use, I just keep tabs on it since there’s a lot of posts about this.

​@Francesco277711048b98 your issue may be related to this thread