Microsoft gives up on users experiencing problems updating their Windows 11 machines. Now recommends a "manual correction"
-
Some of them just don't want to take responsibility if they do something wrong under your instructions.
-
I recommend setting up whatever your alternative is a little before committing to ease the transition a bit. It's different, and it's good to fall back to something else for a bit if you get frustrated.
-
MS Office's lie of WYSIWYG and the idiotic requirements to follow absurdly complicated formatting guidelines and them not rendering the same from system to system or even correctly is the most brutal offender. If we used simplistic markdown without page-breaking in the GUI, there could've been no point to buy Office, but we don't, and itso hsppens I had encountered many times where some arbitrary cosmetic request like 'you can't have less than X lines per page' caused people toy with formatting or rewriting their documents... only for it showing differently on the other side >:ç Thus leading to even worse things like PDF.
It being the most used piece of office software renders the voluntary switch close to impossible.
-
At least set it outside your DHCP range.
I have my DHCP set to use from
.100and up, and my static addressee are in the.1-99range.I still set it through my router so I have a place to look up which one is which (they're piling up), but they're all in that range.
-
It's the only possible solution. The issue with Windows version to version is they merge shit into the base without worrying about how it affects the codebase as a whole. That's why we have 2-3 different ways to access different menus.
-
Microsoftatemyface
-
-
-
-
How you set it can vary depending on what you're running. Linux is all about choice, and choice means multiple ways to do a thing. Places to look:
raspi-config- catchall CLI tool on Raspbian, not sure if it covers both of the following, but it's a good option to start with- /etc/network/interfaces - the Debian way to do things
- Network Manager - usually used for desktops, but can be used by servers; if the first two don't work, try this
But you could also have installed something different. If you post your OS and version and what you're running on it, I can give better advice.
That said, normal networking rules apply:
- don't set a static lease in your DHCP range, or you could get conflicts, which can look like it's not working
- consider using DHCP and setting the static lease through your router; use the MAC address and you'll never need to mess with network settings on the Pi
- if you set on the pi, make sure everything is correct (netmask, gateway, interface)
-
So you're saying you don't like the choice in Linux? On a given distro, there's usually one right way and maybe 2 other ways. Learn the right way for your setup and you're good.
If you're using Network Manager, do it the Network Manager way. If you're using Debian as a server, do it the Debian way (`/etc/network/interfaces). If you're using SUSE, do it the SUSE way (YaST).
If you don't want to deal with it, use DHCP (usually default) and set the static lease on your router using the MAC address. That's better anyway because you can change all of your static leases in one spot if you ever need to.
-
2 is usually install, using a live version of Linux kinda sucks.
-
My guess is that they’ll keep adding to WSL until Windows is just a legally ambiguous closed-source wrapper around Linux. They’ll make the GPL’d part so convoluted that they’re the only organization able to maintain it, which will force people to continue using their proprietary wrapper. Basically Android but for PCs.
-
I’ve ran
I've run
-
I'm approaching 60.
How old are you? I'm guessing you are like 40. You don't even know who Joel is.
-
It's entirely possible.
-
I agree. They need to be either pressured or abandoned.
I feel like they would need to rewrite it completely in that case, partially because no one knows how their legacy code works and partially because it's completely broken.
Google with it's billions and a promise of more free data did great with how office formats work. They set some little limits of what user can do compared to MS Word so ending up with a broken table or whatever is harder, and they aslo strong-armed their way into adoption with their obvious mechanics of real-time collaboration.
I'm not sure about MS users coming to Linux, but their marketshare was already bled by Google. And if in some scenario Google releases their own internal XML format for these, I guess it'd work too.
-
That manual correction: installing Linux.
-
I've had my enterprise-distro linux machines updating by cron for 22 years. I had two glitches in those 20 years, too, just like you. But in addition to my two glitches - I had to bring in one unlisted dep for cobbler and also correct the smb.conf's old format on another box - in 20 years, I also got
- out-of-the-box
- do-nothing patch runs
- trivial back-out if I needed it
And while I know your numbers are excellent, I simply haven't had to DO ANYTHING since deploying some boxes. They patch, they bounce later on a weekend if they need it ('needs-rebooting' is centralized because ALL software installs are) and I can patch while under load because linux write-locks instead of read-locking. My effort is to check 'some time later' and ensure things are working in ways nagios doesn't catch.
Printer issues? Nah. Supply thing. App not working because java/perl/python/DLLs rug-pulled a dependency? Proper packages list hard dependencies, so that cobbler thing is a bug not an expectation. Network offline? nah. Reboots? timed at 3 minute downtime (1 min before systemd), or 7 minutes if I just updated 1gb of gitlab install because it starts like a manatee.
It's really a different world; and while I've teased the heck out of my windows peers, it's a true statement.
-
There's a massive difference between the average Windows user and the average PHP developer. It's a false equivalence.
The regular computer user who just needs their apps to run won't likely make the effort to enter an entirely new ecosystem as long as those apps run. And when they break? They'll reinstall Windows or pay someone else to fix it.
I love shitting on Microsoft as much as the next penguin, but they're not idiots. Even if some of their decisions are questionable, Windows is still a major part of their business, and they won't just let it degrade to a point where Linux converts are a significant threat to their profit.
