Problem: “The current nozzle setting does not match the slicing file. Continuing to print may affect print quality. It is recommended to re-slice before starting the print.”
Firmware: 01.11.00.00
Printer: X1C
After upgrade to 01.11.00.00 Firmware, I would get the message below:
“The current nozzle setting does not match the slicing file. Continuing to print may affect print quality. It is recommended to re-slice before starting the print.”
Reverted back to 01.10.00.00 and the issue was resolved.
That behavior is expected when there is only one nozzle, as in version 01.10.00.00, but two nozzles (standard and high‑flow) in later firmware versions. A more robust approach would have been to treat previously sliced files as using the standard nozzle, since no other nozzle type existed before the latest release.
ambu Studio 2.4.0.70 crashes instantly after installing Network Plugin (Windows 11)
System information
OS: Windows 11 (64-bit)
RAM: 32 GB
GPU: NVIDIA GTX 1080 Ti
Software version
Bambu Studio: 2.4.0.70
Problem description
Bambu Studio works correctly until the Network Plugin is installed.
As soon as the Network Plugin is installed, the application crashes during startup.
When launching Bambu Studio, the “Loading configuration” screen appears for about 1–2 seconds, after which the application closes without displaying any error message.
If the Network Plugin is uninstalled, Bambu Studio starts and works normally again.
Steps to reproduce
Install Bambu Studio 2.4.0.70
Launch Bambu Studio → works correctly
Install the Network Plugin
Launch Bambu Studio
Application closes immediately during startup
This behavior is 100% reproducible on my system.
What I already tried
Full uninstall and reinstall
Running Bambu Studio as administrator
Firewall disabled / firewall rules checked
Antivirus exclusions added
Clean reinstall without Network Plugin (works)
Reinstall with Network Plugin (crashes again)
Windows crash details (Event Viewer / Reliability Monitor)
0xc0000005 indicates an access violation, meaning the crash occurs inside BambuStudio.dll itself, not in Windows, drivers, firewall, or antivirus components.
Important observations
The crash occurs only when the Network Plugin is installed
No GPU, firewall, or permission errors are logged
Windows often does not log a standard “Application Error” because the process is terminated at a low level
Downgrading to Bambu Studio 2.3.x with its matching Network Plugin also does not work on this system
Current status
At this point, I am unable to find any working solution.
The application is only usable without the Network Plugin, which disables network/cloud functionality.
I have been trying to figure this out for hours. I did a whole reset thinking my child removed a file. Still didn’t work.
Where you able to figure it out?
Exact same thing happening to me: right after network plugin installation the entire BS interface disappears from my screen. Have done as the report suggests and no luck. BS works fine on my Windows laptop on the same network. I can communicate with my printer and submit jobs. And I can access my printer’s camera through the laptop. Not on the Workstation. Whatever it is is happening on my workstation. BS worked fine a couple days ago but something changed yesterday. Does anyone know if an update tot he network plugin got pushed overnight?
I know, it’s just that you should only rely on the last numbers xx.xx.06.63. Bambu can’t keep having the first four digits right, nor that they regularly update the wiki.
At the time of my message the real latest was 00.00.06.75 and my AMS1 is now currently on 01.00.06.83, at least this time it makes sense but I’m sure the next one will be something like 00.00.06.95 or 00.01.06.95 if that makes sense…
Why would they “not keep having the first numbers right”?
Do you understand how software versioning works? Because I am intimately familiar with software dev.
It is not rocket science to get versioning correct.
Not to mention the fact that multiple people in this thread have mentioned that moving to that firmware was a regression - a strong indicator that it was in fact moving to an older version.
So yes, I do actually expect Bambu to both publicly publish their change, log for every version as well as the proper version number, particularly within the actual printer UI.
Ok, not trying to be a jerk about this but I’m going to do my best to explain how versioning works and why this isn’t just a typo.
Version releases (commonly referred to as just “versions”) are generally managed through Git version control and the version number is generated, programmatically as part of a new branch for that version, once the branch is merged there is generally a pipeline that builds the latest release and pushes it out to wherever they provide their release downloads.
The version number is stored as a variable somewhere in your code, generally in a top-level project configuration file as a variable and/or key/pair value and is probably even part of the Git branch name.
All of this is to say they would have to screw up by missing thy version number in a lot of places (while having it programmatically pulled from likely a single variable) and never notice it for it to get all the way to the release stage with the wrong version number to be displayed in your printer UI incorrectly…and even then it would be pulled programmatically, it wouldn’t just be a typo because Bob the firmware guy typed it in wrong.
So until Bambu acknowledges this and confirms it’s a typo, I don’t buy it for a second.
I’m not going to waste too much time on thiis, my AMS always worked without issue from one firmware to the other whatever the version shown as latest update on P1S and H2D.
Pease do the following and may be you’ll understand what I mean.
Use bambu handy and click on the hamburger on the top right, then click on firmware version, make a note of your installed AMS1 firmware and then click on « I want to downgrade to a previous version » at the bottom of the page.
Look at the versioning of the AMS firmwares from top to bottom of the previous version 1, previous version 2, etc. Can’t you see anything weird?
I have exactly same problem on my P2S with 01.01.01.00 firmware. Tried to downgrade to 01.01.00.00 - faced this issue also.
The only difference is, that it is not possible to switch video resolution for P2S. This issue reproduces randomly on long prints (>2h) once per 2-3 days. HMS_0C00-0100-0002-0008 error appears on printer, video became unavailable and just after power cylcling printer camera start working immediately
Problem: Studio cannot print plate using bambu tpu-ams Firmware Version: 01.01.05.00 (and reverted 01.01.00.00, see below) Printer: Bambu Lab H2C Steps to reproduce:
Bambu Studio, single Material model using TPU for AMS.
Just to .05 firmware via printer touch screen
Model sliced ok but when printing plate an error about updating to latest firmware occurred when it was the upgrade that caused the issue.
Used handy app to revert to .00 firmware and error persisted even though the .00 firmware had never had an issue before.
After each firmware change, the device and software were each restarted
Log file: Export the log file following this guide: Not sure how without external storage device. Other information:
Filament loaded from the spool holder, and not via AMS HT to left nozzle
Used Bambu Lab TPU-AMS Yellow.
Printing in petG worked fine with both versions of the firmware.
Have you tried loading your TPU-AMS on the right nozzle. There is a new firmware coming to allow TPU to be fed from both nozzles but it’s not there yet. It is possible BS treats any TPU (including AMS) as not possible on the left nozzle which may explains it (a bug as far as TPU-AMS is concerned). Try the right nozzle to see if that’s the case
Good idea. That has worked, Thank you.It will print through the right nozzle (.00 firmware, I am staying away from .05 if I can get it working for now). At least I can now get the TPU printing jobs out of the way.
I am surprised that this was released, I would have thought that it would have been caught in QA/Beta.