Skip to main content
Improved the restart procedure explanation.
Source Link
ikaerom
  • 826
  • 10
  • 21

This did the trick on my side:

  1. sudo sfltool resetbtm (in a terminal of your choice).
  2. Then rebootReboot.
  3. ThenMost items will legitimately re-register themselves in the database again.
  4. In some instances: re-register/re-install your tools toapplications which did not propagate the LoginItems, LaunchAgents and LaunchDaemons mechanisms properly. See below for some explanations.

This is how a successful reset looks like:

$ sudo sfltool resetbtm
2023-02-17 10:44:42.996 sfltool[84683:34363723] Database reset.

Note: this will irrevocably reset your whole database of registered LaunchAgents, LaunchDaemons, and LoginItems. For all registered users. At least until you reboot.

To kind of back up or see what you need to re-install again after this, use the following command:

$ sudo sfltool dumpbtm
[... output with all the database entries ...]

Normally, after reboot, most if not all of these entries should be added back properly. If you miss an auto-start application, check back with this list you prepared before resetting the database, and re-install the application accordingly.

The sfltoolis essentially taking care of the following aspects:

com.apple.LSSharedFileList.RecentServers
com.apple.LSSharedFileList.SharePoints
com.apple.LSSharedFileList.FavoriteItems
com.apple.LSSharedFileList.SavedSearches
com.apple.LSSharedFileList.ManagedShared
com.apple.LSSharedFileList.RecentHosts
com.apple.LSSharedFileList.RecentDocuments
com.apple.LSSharedFileList.SessionLoginItems
com.apple.LSSharedFileList.AutomountedServers
com.apple.LSSharedFileList.SFLLaunchdJobs
com.apple.LSSharedFileList.SFLServiceManagementLoginItems
com.apple.LSSharedFileList.FavoriteServers
com.apple.LSSharedFileList.FavoriteVolumes
com.apple.LSSharedFileList.ApplicationRecentDocuments
com.apple.LSSharedFileList.iCloudItems
com.apple.LSSharedFileList.DockApplications
com.apple.LSSharedFileList.GlobalLoginItems
com.apple.LSSharedFileList.RecentApplications
com.apple.LSSharedFileList.NetworkBrowser
com.apple.LSSharedFileList.ProjectsItems
com.apple.LSSharedFileList.ManagedSessionLoginItems

Alternatively, you might opt to install blockblock: https://objective-see.org/products/blockblock.html, and simply block repeated 'installations' of the same application. I haven't tried it though.

Some background on the currently chosen notification design by Apple: https://support.apple.com/en-gb/guide/deployment/depdca572563/web

I wish Apple fixed this (the issue was introduced with Ventura stock and is still present in Ventura 13.2.x). Many users are having an unpleasant experience regarding this:

This did the trick on my side:

  1. sudo sfltool resetbtm (in a terminal of your choice).
  2. Then reboot.
  3. Then re-register/install your tools to propagate the LoginItems, LaunchAgents and LaunchDaemons mechanisms.

This is how a successful reset looks like:

$ sudo sfltool resetbtm
2023-02-17 10:44:42.996 sfltool[84683:34363723] Database reset.

Note: this will irrevocably reset your whole database of registered LaunchAgents, LaunchDaemons, and LoginItems. For all registered users.

To kind of back up or see what you need to re-install again after this, use the following command:

$ sudo sfltool dumpbtm
[... output with all the database entries ...]

The sfltoolis essentially taking care of the following aspects:

com.apple.LSSharedFileList.RecentServers
com.apple.LSSharedFileList.SharePoints
com.apple.LSSharedFileList.FavoriteItems
com.apple.LSSharedFileList.SavedSearches
com.apple.LSSharedFileList.ManagedShared
com.apple.LSSharedFileList.RecentHosts
com.apple.LSSharedFileList.RecentDocuments
com.apple.LSSharedFileList.SessionLoginItems
com.apple.LSSharedFileList.AutomountedServers
com.apple.LSSharedFileList.SFLLaunchdJobs
com.apple.LSSharedFileList.SFLServiceManagementLoginItems
com.apple.LSSharedFileList.FavoriteServers
com.apple.LSSharedFileList.FavoriteVolumes
com.apple.LSSharedFileList.ApplicationRecentDocuments
com.apple.LSSharedFileList.iCloudItems
com.apple.LSSharedFileList.DockApplications
com.apple.LSSharedFileList.GlobalLoginItems
com.apple.LSSharedFileList.RecentApplications
com.apple.LSSharedFileList.NetworkBrowser
com.apple.LSSharedFileList.ProjectsItems
com.apple.LSSharedFileList.ManagedSessionLoginItems

Alternatively, you might opt to install blockblock: https://objective-see.org/products/blockblock.html, and simply block repeated 'installations' of the same application. I haven't tried it though.

Some background on the currently chosen notification design by Apple: https://support.apple.com/en-gb/guide/deployment/depdca572563/web

I wish Apple fixed this (the issue was introduced with Ventura stock and is still present in Ventura 13.2.x). Many users are having an unpleasant experience regarding this:

This did the trick on my side:

  1. sudo sfltool resetbtm (in a terminal of your choice).
  2. Reboot.
  3. Most items will legitimately re-register themselves in the database again.
  4. In some instances: re-register/re-install applications which did not propagate the LoginItems, LaunchAgents and LaunchDaemons mechanisms properly. See below for some explanations.

This is how a successful reset looks like:

$ sudo sfltool resetbtm
2023-02-17 10:44:42.996 sfltool[84683:34363723] Database reset.

Note: this will irrevocably reset your whole database of registered LaunchAgents, LaunchDaemons, and LoginItems. For all registered users. At least until you reboot.

To kind of back up or see what you need to re-install again after this, use the following command:

$ sudo sfltool dumpbtm
[... output with all the database entries ...]

Normally, after reboot, most if not all of these entries should be added back properly. If you miss an auto-start application, check back with this list you prepared before resetting the database, and re-install the application accordingly.

The sfltoolis essentially taking care of the following aspects:

com.apple.LSSharedFileList.RecentServers
com.apple.LSSharedFileList.SharePoints
com.apple.LSSharedFileList.FavoriteItems
com.apple.LSSharedFileList.SavedSearches
com.apple.LSSharedFileList.ManagedShared
com.apple.LSSharedFileList.RecentHosts
com.apple.LSSharedFileList.RecentDocuments
com.apple.LSSharedFileList.SessionLoginItems
com.apple.LSSharedFileList.AutomountedServers
com.apple.LSSharedFileList.SFLLaunchdJobs
com.apple.LSSharedFileList.SFLServiceManagementLoginItems
com.apple.LSSharedFileList.FavoriteServers
com.apple.LSSharedFileList.FavoriteVolumes
com.apple.LSSharedFileList.ApplicationRecentDocuments
com.apple.LSSharedFileList.iCloudItems
com.apple.LSSharedFileList.DockApplications
com.apple.LSSharedFileList.GlobalLoginItems
com.apple.LSSharedFileList.RecentApplications
com.apple.LSSharedFileList.NetworkBrowser
com.apple.LSSharedFileList.ProjectsItems
com.apple.LSSharedFileList.ManagedSessionLoginItems

Alternatively, you might opt to install blockblock: https://objective-see.org/products/blockblock.html, and simply block repeated 'installations' of the same application. I haven't tried it though.

Some background on the currently chosen notification design by Apple: https://support.apple.com/en-gb/guide/deployment/depdca572563/web

I wish Apple fixed this (the issue was introduced with Ventura stock and is still present in Ventura 13.2.x). Many users are having an unpleasant experience regarding this:

Source Link
ikaerom
  • 826
  • 10
  • 21

This did the trick on my side:

  1. sudo sfltool resetbtm (in a terminal of your choice).
  2. Then reboot.
  3. Then re-register/install your tools to propagate the LoginItems, LaunchAgents and LaunchDaemons mechanisms.

This is how a successful reset looks like:

$ sudo sfltool resetbtm
2023-02-17 10:44:42.996 sfltool[84683:34363723] Database reset.

Note: this will irrevocably reset your whole database of registered LaunchAgents, LaunchDaemons, and LoginItems. For all registered users.

To kind of back up or see what you need to re-install again after this, use the following command:

$ sudo sfltool dumpbtm
[... output with all the database entries ...]

The sfltoolis essentially taking care of the following aspects:

com.apple.LSSharedFileList.RecentServers
com.apple.LSSharedFileList.SharePoints
com.apple.LSSharedFileList.FavoriteItems
com.apple.LSSharedFileList.SavedSearches
com.apple.LSSharedFileList.ManagedShared
com.apple.LSSharedFileList.RecentHosts
com.apple.LSSharedFileList.RecentDocuments
com.apple.LSSharedFileList.SessionLoginItems
com.apple.LSSharedFileList.AutomountedServers
com.apple.LSSharedFileList.SFLLaunchdJobs
com.apple.LSSharedFileList.SFLServiceManagementLoginItems
com.apple.LSSharedFileList.FavoriteServers
com.apple.LSSharedFileList.FavoriteVolumes
com.apple.LSSharedFileList.ApplicationRecentDocuments
com.apple.LSSharedFileList.iCloudItems
com.apple.LSSharedFileList.DockApplications
com.apple.LSSharedFileList.GlobalLoginItems
com.apple.LSSharedFileList.RecentApplications
com.apple.LSSharedFileList.NetworkBrowser
com.apple.LSSharedFileList.ProjectsItems
com.apple.LSSharedFileList.ManagedSessionLoginItems

Alternatively, you might opt to install blockblock: https://objective-see.org/products/blockblock.html, and simply block repeated 'installations' of the same application. I haven't tried it though.

Some background on the currently chosen notification design by Apple: https://support.apple.com/en-gb/guide/deployment/depdca572563/web

I wish Apple fixed this (the issue was introduced with Ventura stock and is still present in Ventura 13.2.x). Many users are having an unpleasant experience regarding this: