Okay, that’s enough for me, I’m out after this one… I was giving you the benefit of the doubt that maybe you read too fast or something. Now I’m not sure you’re reading at all. 
Nothing to do with “supporting an extreme minority”. It really is as simple as “Don’t screw with or break my property for me after I’ve purchased it.”
Ok, and does the previous firmware and software combination from before this update still continue to work?
If yes, then your product is still working just fine like it did before the update
Updates can change the system requirements and render certain machines unable to use the newest version of something, it happens a lot, i get that you don’t like that and thats perfectly valid, nobody is saying you’re not allowed to be annoyed by it, but those choices are made with market share in mind, you have to weigh up the costs of continuing to support something versus the benefit gained from keeping those users around
I would like to think you’re smart enough to know that this is the case and that you are just venting for the sake of venting, which again is fine, get that stress out of your system, but ultimately we both know that any and all decisions made come down to money at the end of the day and that when something costs more to maintain than it generates in revenue it ends up as a potential removed feature
If your windows 10 PC doesn’t have a TPM module and therefore isn’t supported to be upgraded to windows 11, is microsoft “screwing with your property” by releasing windows 11?
This is an interesting tangent. It goes a little bit off topic so I don’t know if it should be broken out of the thread… but maybe yes? Yeah I guess they are doing something a bit evil there.
Nobody expects indefinite support of old hardware that becomes truly obsolete, but this kind of thing seems to be a growing problem. I don’t really have a good solution but I think it’s a conversation more people should be having.
One could argue that the lack of a TPM is a reason for Microshaft to deprecate older hardware. But does that seem like a good reason to deprecate it? Think of all the e-waste and/or insecure devices running W10 which will continue to be used for years, as we all know will happen. Did they really need to do this for Windows 11? One of the largest market cap companies in the world couldn’t afford continued support? 
It sounds kind of sketchy, yes?
From a Windows user’s perspective they effectively EOL’d a lot of working hardware. I don’t know how old that stuff is today, but it works perfectly fine still, so doesn’t it feel a little abusive? It sure would to me if I used WIndows. (In fact from my perspective they’ve done Linux a favor, to spur a few people to jump ship, but that doesn’t make what MS did seem any less evil.)
And yes here I am as a “minority” Linux user defending the “majority” Windows users a little (a courtesy that we rarely get in return). I suppose this is why legal structures are often created to protect minority interests in democracies (US Electoral College!).
So based on what I know, MS does seem to be treading on some thin ice doing what they did, in my opinion. I’d imagine that if it becomes a habit, all this extra e-waste and throwing away of perfectly working hardware might get the attention of some legislators. (Not that they are usually helpful for anyone.) Manufacturers got away with this for phones for a long time. Are we going to throw desktops and laptops into that too now and replace them all every few years?
And just for the record, I really hate to even suggest something like a law to fix a problem like this. I’d rather not, actually. But it’s a difficult and growing problem that out of frustration makes me wonder if we need to fight dirty tricks back with more dirty tricks.
Also for the record, I’m not saying BL has actually done something like this yet in the Linux context, but they’re too close for comfort. And they did try to pull the rug out from LAN mode users, until they backtracked with “Dev mode”.
And Windows 10 is pretty much at EOL.
Yup its support comes to an end soon, there will be optional paid support extensions but even it will start to be deprecated yeah
can someone give me an TL;DR how it is now going on with the topic?
and is Orcaslicer now working with newest update ?
Looks like bambu didn’t focus on security, but rather walled-garden approach. Since walled garden has no benefits to the users, orca devs rejected PR that would allow “seamless” sending via electron bloatware, however the “old” method still works actually seamlessly if you haven’t updated your firmware (or if you have, you stwitched to “dev” mode instead of some weirdo blocked “lan” that calls home)
Having been forced to update a couple of days ago, both Studio and Orca work with my X1.
I did need to enable LAN- and Dev-modes though.
The latter is what I expect this whole malarkey is all about as you need to co firm that you understand that Bambu is not liable for issues arising in Dev-mode.
They are probably concerned about being held responsible for damages (including business losses) that they had no chance of averting due to user choices.
Whatcha mean forced to update? 
That’s what I was gonna ask too.
is a worrisome statement. Care to elaborate (a bit more) @EnoTheThracian ?
Not to speak on behalf of @EnoTheThracian, but I used this term in a previous post and believe I explained myself. Bambu Support forced me to upgrade my P1P because they refused to even consider my tech support request until I did. I mentioned this in a previous thread where I called out Bambu’s bullying tactics—they pushed me two revision levels past the stable version I had, with no downgrade path before the primary rev.
I was on 1.04, and they forced me onto 1.06. Notably, Bambu Handy only allows downgrades within the same major 1.0x release levels, which is completely absurd, unwarranted, and goes against industry-standard practices.
What’s worse, there is no technical reason for this policy—except that 1.03 vs 1.04 is where forced MakerWorld features were enabled. This strongly suggests that Bambu has an unspoken agenda, and their lack of transparency about these practices is at the heart of my distrust.
It was nothing as dramatic for me or intentional from Bambu’s side.
I was facing multiple issues at the same time while being rather overburdened with a growing task list. Also, my IT skills are OK for simple programming, but that is pretty much it. At Uni, IT lectures usually started with “Good morning”, but after that, the Prof continued in a language that is still a mystery to me 
So with only a short break available to me, I had to address my connection issues all at the same time rather than going through the motions step-by-step to find the root cause. I ran through:
As you can see, different root causes could have prevented me from getting sensible slicing results (time estimates were way over the top in both Studio and Orca but fortunately I had run enough pre-trials to understand that they overestimated by a factor of 2) and being able to send the jobs to the printer.
Most importantly, at least half of the problem chain was sitting in front of the screen
So having felt the need to use the sledgehammer rather than painstakingly hunting a jumble of smaller bugs, I am now in Dev-Mode and enjoying Orca again.
It does serve as a reminder that “hard” methods are not always needed to force an action though!
Addendum @Olias
I had a similar experience with the 1.4 firmware update which preceded the death of my first X1. I am still convinced that I had an unlucky component combination where the Lidars firmware was intended to be “upgraded” by changing the hardware…
Bambu’s reaction to the release of X1+ seemed to me to be driven by absolute terror from the possibility of even remotely being held accountable for user actions even remotely out of their control. That also explains (to me) why Bambu is going to so much trouble to get the users to provide a waver if they dip their toes outside the Bambu perimeter.
I find it quite flabberghasting that Bambu even goes as far as making their next, expensive flagship completely unattractive for commercial users. Most X1’s I have seen outside my home are in a production supporting or commercial R&T environment… If these customers can not consider the H2D for networking reasons, the potential market gets much, much smaller…
I think they really have to be terrified of legal repercussions due to remotely possible user actions. I won’t judge that though due to lack of competence on my side.
I remember those days. 
Thanks for the explanation.
There’s a technical definition for what you experienced “A Very Bad Day”
You took the words literally out of my mouth…
Very nicely summarized
So does Developer mode allow a complete bypass of Bambu Connect for Orca Slicer, Home Assistant, etc?
It seems to me there is some gray area between control the printer offline and Third party software in that statement that isn’t clear to me.
A cynic might say that it almost seems like fall out at hobbling their pre-existing BS connectivity paths may incentivise buying their new printer.
Devil in the details:
* there refers to the fact that in developer mode the use of laser&cutter module is not availalble: