Win 10 2004 is still a steaming pile of ...
-
Installed yesterday on my desktop, and it looks fine - until I try to work on it this morning and find it no longer recognises my NAS exists, much less has shares. "You need permission to access this resource" for mapped drives that worked fine yesterday, and which work fine on my 1909 build Surface. OK ... revert to previous version ... come on MS, I thought you'd fixed this! Didn't this happen back in 2017 as well? [edit] Reverted to 1909 - didn't take as long as I thought it might , less than 5 minutes. And ... I have all shares back. FES, MS ... :sigh: [/edit]
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
I am holding off 2004 until either compelled to or until Microsoft withdraw it and release something that won't break my machines.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
I am holding off 2004 until either compelled to or until Microsoft withdraw it and release something that won't break my machines.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
Be ready to wait a long time...I'm not always convinced any newer release these days is necessarily better than any previous version. At this stage in its lifetime, you'd think Windows had reached a point where things would improve. I'd be perfectly okay with MS spending a full year not adding any new "feature" nobody asked for, and dedicating the internal team's time to do nothing but fix what's known to be broken. The fact that they keep introducing new icons, but break basic functionality with every new release, tells me they've run out of ideas anyway. How one affects the other...I can only speculate.
-
Be ready to wait a long time...I'm not always convinced any newer release these days is necessarily better than any previous version. At this stage in its lifetime, you'd think Windows had reached a point where things would improve. I'd be perfectly okay with MS spending a full year not adding any new "feature" nobody asked for, and dedicating the internal team's time to do nothing but fix what's known to be broken. The fact that they keep introducing new icons, but break basic functionality with every new release, tells me they've run out of ideas anyway. How one affects the other...I can only speculate.
They are hoping the icons gain self-awareness, and then fix the bugs for them.
-
Installed yesterday on my desktop, and it looks fine - until I try to work on it this morning and find it no longer recognises my NAS exists, much less has shares. "You need permission to access this resource" for mapped drives that worked fine yesterday, and which work fine on my 1909 build Surface. OK ... revert to previous version ... come on MS, I thought you'd fixed this! Didn't this happen back in 2017 as well? [edit] Reverted to 1909 - didn't take as long as I thought it might , less than 5 minutes. And ... I have all shares back. FES, MS ... :sigh: [/edit]
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
I seem to remember an update a few revs back had a problem with network shares. The fix was to load something into the registry. Could this be the same issue returning to haunt us?
"They have a consciousness, they have a life, they have a soul! Damn you! Let the rabbits wear glasses! Save our brothers! Can I get an amen?"
-
Be ready to wait a long time...I'm not always convinced any newer release these days is necessarily better than any previous version. At this stage in its lifetime, you'd think Windows had reached a point where things would improve. I'd be perfectly okay with MS spending a full year not adding any new "feature" nobody asked for, and dedicating the internal team's time to do nothing but fix what's known to be broken. The fact that they keep introducing new icons, but break basic functionality with every new release, tells me they've run out of ideas anyway. How one affects the other...I can only speculate.
Sadly you are probably going to turn out to be correct. Around 10 or more years ago there was a similar update which broke a lot of machines. When I am feeling lucky I will take an image and give it a go, I have the sense that it will be another few months until I feel lucky. As for breaking Windows when they just supply an icon update - I am not surprised. I work on a huge complex series of tightly coupled codebases and it's not rare for someone to break some part of the system by a seemingly unrelated change. Refactoring code pretty much always breaks something. What Microsoft obviously don't have are comprehensive unit or user tests. Which does not make them too different to many other software development companies.
“That which can be asserted without evidence, can be dismissed without evidence.”
― Christopher Hitchens
-
Installed yesterday on my desktop, and it looks fine - until I try to work on it this morning and find it no longer recognises my NAS exists, much less has shares. "You need permission to access this resource" for mapped drives that worked fine yesterday, and which work fine on my 1909 build Surface. OK ... revert to previous version ... come on MS, I thought you'd fixed this! Didn't this happen back in 2017 as well? [edit] Reverted to 1909 - didn't take as long as I thought it might , less than 5 minutes. And ... I have all shares back. FES, MS ... :sigh: [/edit]
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
Installed yesterday on my desktop, and it looks fine - until I try to work on it this morning and find it no longer recognises my NAS exists, much less has shares. "You need permission to access this resource" for mapped drives that worked fine yesterday, and which work fine on my 1909 build Surface. OK ... revert to previous version ... come on MS, I thought you'd fixed this! Didn't this happen back in 2017 as well? [edit] Reverted to 1909 - didn't take as long as I thought it might , less than 5 minutes. And ... I have all shares back. FES, MS ... :sigh: [/edit]
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
Automatic updates on my bread-winning machine are turned off. And I'm now running Internet Explorer on my Surface, 'cause the "new" Edge can't.
It was only in wine that he laid down no limit for himself, but he did not allow himself to be confused by it. ― Confucian Analects: Rules of Confucius about his food
-
Installed yesterday on my desktop, and it looks fine - until I try to work on it this morning and find it no longer recognises my NAS exists, much less has shares. "You need permission to access this resource" for mapped drives that worked fine yesterday, and which work fine on my 1909 build Surface. OK ... revert to previous version ... come on MS, I thought you'd fixed this! Didn't this happen back in 2017 as well? [edit] Reverted to 1909 - didn't take as long as I thought it might , less than 5 minutes. And ... I have all shares back. FES, MS ... :sigh: [/edit]
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
For every single windows version since W98 there was somebody complaining about updates. If MS listened to customers, we would still be using DOS.
Or ... they might fix bugs instead of adding features and papering over the cracks? When an update introduces breaking changes, it's pretty understandable that people comment / warn / complain.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
Or ... they might fix bugs instead of adding features and papering over the cracks? When an update introduces breaking changes, it's pretty understandable that people comment / warn / complain.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
-
Installed yesterday on my desktop, and it looks fine - until I try to work on it this morning and find it no longer recognises my NAS exists, much less has shares. "You need permission to access this resource" for mapped drives that worked fine yesterday, and which work fine on my 1909 build Surface. OK ... revert to previous version ... come on MS, I thought you'd fixed this! Didn't this happen back in 2017 as well? [edit] Reverted to 1909 - didn't take as long as I thought it might , less than 5 minutes. And ... I have all shares back. FES, MS ... :sigh: [/edit]
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
I'm still clinging desperately to Windows 7 but I use my laptop with Windows 10 to participate in home schooling for my granddaughter. We do video calls in Messenger accessed by a URL invoked via Chrome browser. Overnight, Windows 10 decided that Chrome is too insecure to be allowed access to the camera which is great to find out at the start of a rigidly scheduled time window for a video call. It took a while to track down where the camera blockage was coming from but installing Messenger and invoking it directly appeased the Microsloth ^%$^%$. OldBikerPete
-
One might guess that the MS developers have their priorities set by the lawyers. 1. Make it secure 2. Make it more secure. 3. Don't let it violate any copyrights 4. Make sure it lets mother know of any anomalies. 5. etc. 73. make it usable. BTW: an always-on backup device is not a backup against malware. :) I run W10 in virtual machines and keep the NIC off until I need it. Easy to backup, just copy the files from time to time. My surveillance camera systems are still on W7. Would you believe they rebooted to accommodate the "new Edge", tada. I thought updates were a thing of the past.
If you can keep your head while those about you are losing theirs, perhaps you don't understand the situation.
Only two digits in 73. I expected more. Of course 72 is "it's a feature!" and pertains to many things...
-
Installed yesterday on my desktop, and it looks fine - until I try to work on it this morning and find it no longer recognises my NAS exists, much less has shares. "You need permission to access this resource" for mapped drives that worked fine yesterday, and which work fine on my 1909 build Surface. OK ... revert to previous version ... come on MS, I thought you'd fixed this! Didn't this happen back in 2017 as well? [edit] Reverted to 1909 - didn't take as long as I thought it might , less than 5 minutes. And ... I have all shares back. FES, MS ... :sigh: [/edit]
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony "Common sense is so rare these days, it should be classified as a super power" - Random T-shirt AntiTwitter: @DalekDave is now a follower!
Yep. It broke the print spooling so I was unable to print anything at all; it changed font sizes everywhere so that many programs were totally unusable, and many system dialogs were incorrectly sized so that cancel / ok buttons weren't accessible... and more. Have un-installed it three times but, like a virus, it kept coming back. Eventually followed advice on here and setup WSUS pointing to a non-existent server. No more issues since then, but of course no more updates either.
