macOS 27.0.1 Issues

Still getting a black screen when the screen saver is set to engage or when previewing the screen saver. This is on macOS 27.0.1.

Deployment is via Jamf Pro, I created a package from the already installed screen saver file and the preference plist as both are found in the root Library subfolders, set chown to Root:Wheel for both. In tandem, a configuration profile sets the screen saver and other settings as follows:

Domain: com.apple.screensaver

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>askForPassword</key>
	<true/>
	<key>askForPasswordDelay</key>
	<integer>0</integer>
	<key>idleTime</key>
	<integer>900</integer>
	<key>loginWindowIdleTime</key>
	<integer>900</integer>
	<key>moduleName</key>
	<string>CompanyScreenSaver_2026_3</string>
</dict>
</plist>

Not sure what I am missing. I am using the latest version of iScreenSaver. It has worked fine this way for quite some time, no issues with macOS 26.x.

Any thoughts or suggestions?

Thanks.

That plist you set is the old one, which generally isn’t relevant for modern macOS. Did you set up the new plist? It’s in a different location.

See Understanding the macOS Sonoma screensaver plist

for description and instructions.

If you have the new plist set up correctly, then there could be another problem.

As the issue seems squarely with macOS 27, even though System Settings’ GUI shows that the designated screensaver is correct, I do not see it listed in the plist. Yes, I decoded all the base64 items in the plist, and there is no reference to the custom screen saver at all, even though the GUI shows it as correct. Still, a black display is still seen when the saver is enabled.

In addition to deploying the system screen saver file and the preference plist, am I now to add the “com.apple.wallpaper/Store/Index.plist” file as well? I am concerned that if I do that, our deployed Wallpaper might be affected, or if the user changes the wallpaper, it would be altered unexpectedly.

The support information lacks detail to understand the flow, and I am looking for more information or suggestions.

Yes, that’s really the only plist file you need for macOS Sonoma and higher.

The installation flow is basically this:

  • on a test machine, install your screensaver (using the iScreensaver-built installer app). Do a “for all Users” installation as indicated.
  • get the plist, and a copy of the .saver bundle that was installed
  • roll out the .saver bundle and the plist on the target machines.

It’s a long thread, so perhaps you missed it, but these step-by-step instructions begin here: Understanding the macOS Sonoma screensaver plist - #5 by iScreensaver

On a test Mac with the older saver version already installed, used the installer from iScreenSaver directly to create a fresh Index.plist file. Created a DMG of it, using Jamf to deploy it to the user space, along with the package installer for the root level saver file and license plist, a post-script runs to ensure the Index.plist file has the correct ownership of the logged in user, then the killall command for the agent. After which triggers the profile for the legacy com.apple.screensaver domain, which disables the user’s ability to change the screen saver setting (still works).

In my testing this looks like a method. Will test out it on my macOS 27 test subjects, but expect things to be fine. If not, I’ll bang on the door again.

Thanks for the help and guidance.

1 Like

Glad to hear it’s working out - we are here to help if you need it, and if you find any more tricks or hints for installation (with or without Jamf), please consider sharing what you find here on the forums to help others in the community.

For future readers, yes, Rosetta 2 is needed, otherwise your saver will be black.

1 Like

Thanks for this tip! To clarify, this would only be necessary in an installation scenario such as this when the company is doing managed installation - for an end user using the iScreensaver Installer, it would automatically trigger the Rosetta installation during the installation process.

For other notes about Rosetta, please also see this: Disabling Rosetta awareness messages for iScreensaver on macOS 26 Tahoe and 27 Golden Gate using MDM