Reason 2: MacOS Doesn’t Allow ItĪnother reason your desktop wallpaper may continue reverting to default is that your Mac has some bug. As long as you don’t delete the picture again, you shouldn’t have any further issues in this respect. While holding Ctrl, click on the image with your trackpad.Īfter doing each of the above, your background image should change straight away.
Alternatively, you can revisit the website you downloaded it from or – if you haven’t yet emptied it – take the photo out of your computer’s Bin. Step 1: Upload the picture that was your screensaver back to your computer. And only when you restart, you find the wallpaper different from the one you had set. You might not realize this since closing the lid and putting the MacBook to sleep a pretty common practice. In this case, your computer likely chose to reset to the default because the file is missing. If you used a photo from the internet or something you took yourself, you might find that your Mac desktop wallpaper resets after deleting it. I hope it helps.Here’s a list of reasons why your Mac desktop wallpaper won’t stay and how you can fix each of them. Not sure if any of these have an impact in it working, but just sharing for reference.
FileVault has been turned on since the macbook was initialized so that shouldn't be an issue in this case like it was mentioned in previous posts.Try to make sure the image has the same dimensions as a standard macOS static lock screen background - you can use the one in "/Library/Caches/Desktop Pictures//lockscreen.png" as an example.My current screen resolution is 2056x1329 which is the higher scaled resolution available in Display Settings for the built-in Retina XDR display.I'm using Macbook Pro (16-inch, 2021) with the latest version of macOS Monterey (12.1) as of today.The new background should be there by then. Make sure the above mentioned file name is set to ".png".Copy the PNG you want as login window wallpaper to the /Library/Caches folder.Was having the same issue, but looked for possible solutions in the web and found these steps that actually fixed it very quickly, even though they were probably meant for a previous version of macOS:
0 kommentar(er)
