Upgrade mojave to catalina2/13/2024 However, using defaults or Prefs Editor is preferable due to the caching system for app preferences (not to mention being faster). Though based on the above tests, there appears to be little harm in simply deleting ~/Library/Preferences/.plist for step 3 as bernuli originally did then rebooting and checking for updates again. defaults delete LatestMajorOSSeenByUserBundleIdentifier (deletes the lines containing LatestMajorOSSeenByUserBundleIdentifier and from ~/Library/Preferences/.plist).sudo softwareupdate -ignore "macOS Catalina".In two followup comments, bernuli suggested these steps for disabling Catalina and resolving the red notification badge issue: ![]() Users created after running sudo softwareupdate -ignore "macOS Catalina" were not affected by the issue ~/Library/Preferences/.plist did not get created even after such users checked for updates. ~/Library/Preferences/.plist was populated with: LatestMajorOSSeenByUserBundleIdentifier ~/Library/Preferences/.plist was created after checking for updates with the following data (which appeared to correspond to "Security Update 2020-002 10.14.6" and "Safari 13.1"): ProductKeysLastSeenByUserĬhecking for updates on a brand new Mojave install and then running sudo softwareupdate -ignore "macOS Catalina" caused the issue to occur for the current user. Running sudo softwareupdate -ignore "macOS Catalina" on a brand new Mojave install before checking for updates prevented the issue from occurring. On a brand new Mojave install, ~/Library/Preferences/.plist did not exist (nor was there a /Library/Preferences/.plist). I decided to do some testing (TL DR: bernuli was exactly right): The file in question was identified as ~/Library/Preferences/.plist. My guess is that new users created after you run the -ignore should never get the Upgrade notification in the first place. Here is a per user preference file that needs hosing to get rid of notification if software update already ran before you did the ignore. Searching for a better way (as well as an answer as to why the issue did not affect all Mojave users who disabled the Catalina upgrade), I had the good fortune of stumbling onto bernuli's October 12 comment, which offered in part:
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |