Mac App Store purchase button disappears on pointer rollover

Hi gggb,

welcome to this Apple (user-to-user) Community!

Re: Mac Mini M4, Tahoe 26.1. : Mac App Store purchase button disappears on pointer rollover

Try checking you are correctly logged in to your Mac with your Apple Account details you use for the App Store: ie: Go to: Apple menu () > System Settings [your name or "sign in"]

While there: You may or may not have settings in place for purchases

Require a password for purchases in the App Store and other Apple services - Apple Support

Eg: says:

1. "On your Mac, choose Apple menu () > System Settings.
2. Click [your name].
3. Click Media & Purchases.
4. Select the settings that you want for free downloads and purchases. If you have Touch ID turned on for purchases, you won’t see this menu".

__________________________________________________

Then check you are signed in correctly to the App Store :

ie: you should see your name / account at the very bottom of the sidebar

_____________________________________

If still facing the same problem on rollover:

Try updating MacOS to the newest version (contains bug-fixes and security uodates),

Reminder: It's always wise to back-up-your Mac before updating MacOS

To check for updates: Apple menu () > System Settings > General > Software Updates.

_____

Note: If you are trying to purchase an app you've had before:

You may be able to re-download it for free: Redownload apps from Apple - Apple Support

______________

Payment set up:

Apple requires you have a payment method listed in your account for the first time you use the App Store or iTunes, and for some other purchases or downloads..

If you do not have a payment method listed in your Apple Account:

See what payment methods Apple can accept in your country or region:

Payment methods that you can use with your Apple Account - Apple Support

See: How to Add an Apple Account Payment method:

Add a payment method to your Apple Account - Apple Support

All the best :-)

Also try updating Tahoe to the current 26.3 What you are experiencing may have been a bug that has already been addressed.