
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-10-2019 01:53 AM
Hi, I have an installer package that I cannot delete. Before this, it was stuck in a "performing preliminary check" loop despite it actually getting installed at that endpoint.
I found in another post the following steps to end the loop which I followed but didn't work immediately.
- stop lansweeper service
- clear installer logs
- delete the scheduled task at the endpoint
- start the lansweeper service
Eventually the package loop stopped and I no longer saw it returning to the Installer Logs as "performing preliminary checks" and now I am trying to delete the package and recreate it. My thinking is the package is corrupt in some way.
As I go to delete it, I get a warning that it is linked and I am apprehensive to click on "YES" not wanting to leave any corruption laying around in the LS database/tables.
The warning is attached.
Any advice how to proceed to "properly" delete this package?
Thanks,
John
I found in another post the following steps to end the loop which I followed but didn't work immediately.
- stop lansweeper service
- clear installer logs
- delete the scheduled task at the endpoint
- start the lansweeper service
Eventually the package loop stopped and I no longer saw it returning to the Installer Logs as "performing preliminary checks" and now I am trying to delete the package and recreate it. My thinking is the package is corrupt in some way.
As I go to delete it, I get a warning that it is linked and I am apprehensive to click on "YES" not wanting to leave any corruption laying around in the LS database/tables.
The warning is attached.
Any advice how to proceed to "properly" delete this package?
Thanks,
John
Solved! Go to Solution.
Labels:
- Labels:
-
General Discussion
1 ACCEPTED SOLUTION

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-10-2019 03:39 PM
Are you sure that the package is not linked to a scheduled deployment? That what it seems to suggest. You can remove the scheduled deployment and then remove the package.
3 REPLIES 3
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-22-2025 08:25 PM
Same bug here, in 2025. The suggestion of creating a schedule, then delete and remove, worked. Thanks!

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-10-2019 03:39 PM
Are you sure that the package is not linked to a scheduled deployment? That what it seems to suggest. You can remove the scheduled deployment and then remove the package.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-10-2019 05:52 PM
Esben.D wrote:
Are you sure that the package is not linked to a scheduled deployment? That what it seems to suggest. You can remove the scheduled deployment and then remove the package.
I have never used a "Scheduled Deployment" but I headed straight there from your suggestion and I found nothing listed. So, I created a "Scheduled Deployment", linked it to the "Installer Package" in question, saved it, then deleted it.
I went back to "Installer Packages" and was now able to delete it without a warning. Weird but very NICE!
Thank you Esben.D for the suggestion that ultimately led to the fix!
