I haven’t used my P1S for a while (bought a Grizzly metal lathe), so when Bambu Studio loaded up, it prompted me to download and update to 1.9.7.52. I have been running 1.9.3.50 (and still am), so I used the “Download” button on the in-app screen and attempted to install it. This was unsuccessful because it kept giving me an error that Bambu Studio was still running (it wasn’t) and to click “ok” to proceed anyway. When I did the error just kept coming back. I also downloaded the file from GitHub directly, with the same result (yes, I restarted my Win 10 PC). Anyone else have a similar experience? I’ve never had an issue with installing updates, until now.
Have you checked task manager for the process ? in case its been added to the system start up ? and have you tried a manual uninstall first before downloading and installing a fresh copy
Yes, it’s not there. (that’s the first think I checked)
No, it is not in startup. (that’s the second thing I checked)
This is where I’m at now. My one concern is that if I uninstall B.S. will I have a problem Installing the new version (I’m afraid that I’ll get the same error even after I uninstall it, weirder things have happened, it is Windows after all).
Bambu Studio Installation Troubleshooting | Bambu Lab Wiki
The issue might be caused by a problem with the outdated version of Bambu Studio, preventing it from exiting properly. A straightforward solution would be to restart your computer and proceed with the installation.
If you encounter any other issues during the application installation, or if the methods mentioned above do not resolve the problem, please don’t hesitate to contact us for further assistance.
I did restart my PC prior to running the update. I guess the next thing is to uninstall the current version, reboot and then run the install for 1.9.7.52. I’ll report back here whether I was successful or not.
I’m getting the same error while trying to uninstall 1.9.3.50. Uninstall.exe says that B.S. is still running and to click “ok” to continue but the error just keeps coming back.
In cases like this, you’ll want to hunt down the offending modules in task manager and terminate them individually. The error message indicates that BL is running somewhere. I’d look for Bambusource.dll as a probable culprit.
However, one utility that is particularly good at remedying this exact problem is Revo uninstaller. Make sure you create a system restore point before you run it. Revo typically will warn you.
Be careful which link you click on when downloading. You want to download the free version(it’s really trialware or nagware).
After it removes all vestiges of the product you want uninstalled, try reinstalling Bambu Studio and ensure that it is working. Reboot twice just to be sure. Then, uninstall Revo Uninstaller as it has done its job and becomes annoying nagware with constant prompts to purchase the product afterward.
I tried to boot up in safe mode, thinking I could uninstall it then. But Microsoft or HP, in their infinite wisdom, have made it nearly impossible to do that. After following “the directions” all it did was a normal reboot. I tried uninstalling 1.9.3.50 again, and this time it worked. I am now up and running in version 1.9.7.52 and my P1S is printing just fine (and B.S. retained all my user presets). Hopefully this is a one off and I won’t need to go through this again. Olias, thanks for the tip on REVO, I’ll keep that in my back pocket in case there is a next time.
1 Like
Thanks for closing the loop and sharing your success with the group. This actually helps the next person who may run into this.
On a side note, and this may be purely coincidental, prior to uninstalling 1.9.3 my PC had been running verrrrrrrrrrrrrrrrrrrry slowly for about four months. I can’t say that this started after I originally updated to 1.9.3, but it was around the same time. Once I was able to get rid of the previous version of B.S. my PC has returned to its speedy former self. The fact that my computer was reporting that B.S. was running, in the background, even though there was no evidence to support that, it must have been using resources (i.e. CPU usage was low, but disk usage was almost always maxed out). I’m just happy that this issue is resolved, and my computer is back to normal. Thank you for your help and moral support.