Push 2 displays only icon in Ableton 12

[EROC3D]

I upgraded to Ableton 12 and my Push 2 display only shows an icon. The pads light up, its recognized in preferences.
When I open in Ableton 9.7 everything works fine.
I contacted Ableton support, they said to uninstall and clear roaming and local, and I removed references in the device manager...and reinstall, (which I already tried several times), and asked me to get back with a new status report, which I did, then got email that was closed and merged... not sure if I got lost in the system.
They said this was a known issue.
I read and searched and tried many things to no avail. Just seeing a push icon on the screen when in Ableton 12.
Tried the options txt "Push2UseLegacyScript" but that made the push non-responsive. Have been trying to get this working for a week now.

Has anyone found a solution for this that worked?

I am using windows desktop Intel i7-7700k CPU @4.20GHz RAM 48 Graphics card NVIDIA GeForce RTX 4060 (8gb) 64 bit windows 10 pro
also using APC40, MPD26, Push 2, Scarlett 18i20 interface and two midi keyboards.

When using Ableton 9 (where I can see the display screen) it shows that the current firmware is 1.0 build 71.

[EROC3D]

Tried turning on unit with the other controllers off... same result in Ableton 12 - pads light up, Ableton 12 recognizes Push 2 but the display only shows a Push icon with no display functionality.

Plugged into usb 3 port on computer... same result.

Cleared (uninstalled) in device manager... same result.

Tried 4 different USB cables....same result.

Running 4 screens, turned one off to see if it had an impact...same result.

In Ableton 12 settings made sure that Control surface is set to none... also tried listing the Push 2 there... same result.

Tried forcing install of Push 2 driver found in Program Data/Ableton/Live 12 Standard/Redist/push2-display-driver-installer.exe.... same result.

Uninstalled Ableton 12, deleted the AppData and Local files... reinstalled Ableton 12... same result.

When I open in Ableton 9.7 the Push 2 runs perfectly. The display screen works fine.

Has anyone else had this problem, and if so. How did you remedy it?

I read somewhere that someone else had a similar issue and rolled back from 12.2 to 12.1 and it worked for him.

Is it possible to download a version of 12.1? or earlier versions?

Any help would be much appreciated. Thank you.

[EROC3D]

I tried uninstalling again, and installing an earlier version of 12. This did NOT resolve the issue.
I uninstalled that and re-installed the latest version. Same result.

The push 2 is still working fine (display is operational) in Ableton 9.7.

Not sure if the serial number has anything to do with it, but sent that info to tech support.

I re-installed the push audio driver. No change.

Has anyone had this challenge?

(Ableton sees the push 2, the pads light up and are operational, but the display just shows a push icon, the display has no functionality in Ableton 12)

Works fine in Ableton 9.7.

[EROC3D]

Tried downloading version 11. No luck.

[EROC3D]

Tried installing version 10. could not authorize... Push 2 did not work in version 10.
I could use some help if anyone has experienced problems getting the Push 2 going.

[haikuluke]

Yes, I am also having issues suddenly with Push 2. I have tried all the steps you tried. It seems directly related to some sort of firmware update that 12.2 likely pushed into push 2.

I am upset because this is clearly a known issue, if you start to search for this problem you see it is cropping up for people all over the place, reddit, here, etc.

And what this means is that by no fault of the user, an expensive device is being essentially bricked. We shouldn't have to hunt and peck here for answers.

I have a support ticket in with Ableton.

[Rivanni]

Try the following.

Close Live and turn off Push.
Add this line to Options.txt (more info about this file can be found here.)

Code: Select all

-Push2UseLegacyScript

. (on a separate new line, including the first dash.)

This will make the Push 2 be like its old self and will not have any of the new features added in recent years.

Start Live, then turn on Push.
Does the Push start normally with this setting? If so, close Live, turn off Push, and remove the line in Options.txt.
Next, start Live, then turn on Push, and see if Push works this time.

If the Push works, the problem is solved. If not, stick to the line in Options.txt until you hear back from support. Same if none of this works.

[EROC3D]

Thank you Rivanni for your reply.

When I got to the preferences folder in Live 12.2.1 there was already an options file with "-EnableArmOnSelection"

Below that I added the "-Push2UseLegacyScript" line.

I opened 12 and turned on the Push2. The Push2 only shows the Push icon with no other functionality with the exception of seeing the yellow midi lights in Ableton confirm that the pads are sending a midi signal. In preferences, the control surface added the Push2 and Input and Output show Ableton Push 2.
Also the Input Ports and Output ports show up as Ableton Push 2 (Port 2). The box does not show up.

I powered the Push2 off and back on, same result.

I then removed the line "-EnableArmOnSelection" in the Options file and it looks like the same result.

I then renamed the Options file to Options2 so that I could test it with neither option.

The Push2 came to life, the box showed up, Push2 showed up in the Settings, the pads lit up and are functional, the buttons lit up, but the screen only shows the Push icon.

I then set the Options file as it was originally with just the "-EnableArmOnSelection" and got the same result as I did removing the Options file.

Push2 is functional, but the display screen just shows the Push logo.

[EROC3D]

Yes, I am also having issues suddenly with Push 2. I have tried all the steps you tried. It seems directly related to some sort of firmware update that 12.2 likely pushed into push 2.

I am upset because this is clearly a known issue, if you start to search for this problem you see it is cropping up for people all over the place, reddit, here, etc.

And what this means is that by no fault of the user, an expensive device is being essentially bricked. We shouldn't have to hunt and peck here for answers.

I have a support ticket in with Ableton.

Haikuluke,
Sorry to hear you are also having a challenge with this. Glad to know that there are others, as I thought I was going crazy trying to figure this out. I too read nearly all instances on reddit, consulted Grok3, searched the internet for help. I have not yet heard back from Ableton on my support ticket, but have been checking my email every day in hopes of a response with a legit solution. I feel that because the Push2 is an Ableton product that the software should pair seamlessly. I upgraded from 9.7 to 12 in anticipation of being able to use the VST3 products that I purchased, and incorporating the Push 2 with the new improvements made since 9.7. At the moment I am quite frustrated. When functioning properly, I love the Ableton platform. At the moment though, I am in limbo.
I did respond to Rivanni that suggested the Options angle. I had already tried that several different way, but went ahead and tried them again for good measure. I am still showing just a logo screen on the Push2 with pad functionality and the box is showing up in the session view. Let me know if you gain any ground on a solution.

[EROC3D]

In the Preferences in Ableton roaming, in the Push2DisplayProcess.log

I see 3 warning messages that say "could not find font file" then 12 errors that read:

"2025-06-27T15:33:03.814464=error { "message": "could not open usb device, error: Could not find Push II USB display device : (could not get usb device list - LibUsb error: "LIBUSB_ERROR_NO_DEVICE") attempt: 1 sleep: 1000" }"

Could this be pointing at the problem?


also there is a Push3.log file there as well that seems to be logging the challenges. Tons of data.

[EROC3D]

I tried downloading zadig and ran as administrator, selected show all, and found the USB for push2 and chose replace driver with WinUSB, that did not do the trick, so I replaced with libusb-win32, that did not do the trick, so I tried libusbk and that did not solve the issue either.

I then removed these instances from device manager and let the Push auto install, returning to the state in Ableton 12.2.1 in which the Push 2 shows up in the settings, the box shows up in session view, the Push 2 pads and buttons light up, but the Push display only shows the Push icon.

So it does not appear that the USB needs to be updated.

One thing I noted, when I tried registering my push on the Ableton website, it said that my serial number for the Push 2 was not recognized... Is it possible that this could be contributing to the issue?

Note that my Push 2 operates fine when I open it in Ableton 9.7.

I have not heard back from tech support. Which is why I am seeking help from the community in hopes of finding a solution.

Please chime in if you have experienced this issue, and what you did to solve it. Thank you.

[EROC3D]

I SOLVED IT!
Praise the Lord!

I recently updated my graphics card (couple of months ago) So the graphics where being run by NVIDIA
Ableton 12 was looking at the Intel graphics that were part of the original install of my computer which was not operational anymore.

In Apps and Features I noticed a package called ASMEDIA USB Root hub

It was tied to two instances of ASMEDIA USB3 Root hub in an Other file in the device manager. These files showed and error 28, and showed that they were not functioning, and could not be updated.

So I uninstalled the package in Apps and Features, restarted the computer, then uninstalled the instances in the device manager and selected re-scan.

I then turned on the Push 2 and started Ableton 12 and the display screen gave me a big beautiful hello. It is now solved and functioning as intended. I cannot wait to let Tech support know the good news.

I hope this helps anyone with the same challenge.

[Rivanni]

Great you solved it.

It is a known problem mentioned in a knowledge base article, step 6.
https://help.ableton.com/hc/en-us/artic ... en-Windows

[molmoluu]

Yes, I am also having issues suddenly with Push 2. I have tried all the steps you tried. It seems directly related to some sort of firmware update that 12.2 likely pushed into push 2.

I am upset because this is clearly a known issue, if you start to search for this problem you see it is cropping up for people all over the place, reddit, here, etc.

And what this means is that by no fault of the user, an expensive device is being essentially bricked. We shouldn't have to hunt and peck here for answers.

I have a support ticket in with Ableton.

absolutely agree with you and your emotion.

I have basically the same issue on push2 after updating live12.2, with macos15 on MacBook Air m1.
something different is, macros can be showed on my push2 screen, but all the buttons, pads and knobs doesn't work.
I just tried out 12.3 beta version, same results.
after degrading live12.1, it works well again.
you may know all the project and device of live12.2 are not able to be opened by live12.1, which means I am facing a choice, abandon push2 or all my previous presets..

what even annoying is, it's now live12.2.5 version. the issue is still there after 5 times bug fix.

[Birdsaintreal]

I SOLVED IT!
Praise the Lord!

I recently updated my graphics card (couple of months ago) So the graphics where being run by NVIDIA
Ableton 12 was looking at the Intel graphics that were part of the original install of my computer which was not operational anymore.

In Apps and Features I noticed a package called ASMEDIA USB Root hub

It was tied to two instances of ASMEDIA USB3 Root hub in an Other file in the device manager. These files showed and error 28, and showed that they were not functioning, and could not be updated.

So I uninstalled the package in Apps and Features, restarted the computer, then uninstalled the instances in the device manager and selected re-scan.

I then turned on the Push 2 and started Ableton 12 and the display screen gave me a big beautiful hello. It is now solved and functioning as intended. I cannot wait to let Tech support know the good news.

I hope this helps anyone with the same challenge.

You are my hero! For me just uninstalling ASMEDIA USB3 Root hub in device manager did the trick!
Thank you so much!