Read more.Quote:
Post-update Windows will sometimes try to run a process requiring a DLL that isn't installed.
Printable View
Read more.Quote:
Post-update Windows will sometimes try to run a process requiring a DLL that isn't installed.
Jesus, how do these things fall through the cracks...
That's not the only bug. My work laptop (A Thinkpad P1) got bricked by the update and refused to boot. I then spent most of the day on long a tedious phone calls with corporate IT support while they attempted to repair the thing, and when they gave up talking me through re-installing windows. The support guy told me that several other laptops had suffered the same fate.
Forgot that optane was even a thing.
Since Win10 came out, Microsoft have been bring out buggy updates.
And guess who are their free unknowing beta testers ? You and me.
Mean while the tech have remained quiet about this.
Feels mighty strange for me of all people to be defending Microsoft, but software is software so...Quote:
Originally Posted by Tabbykatze
Bugs are given a rating. Some bugs at the highest severity are a "blocker" because they have a chance to lose data or brick the machine, so the presence of such a bug blocks release of the product. Severity might raised if there is no escape from it, or lowered if there is a workaround.
This bug doesn't lose data or force a re-install of Windows, so you are starting at mid level bug at worst.
There is a workaround, so that lowers the severity.
MS can avoid deploying to people who might be impacted by the bug, so that lowers the severity.
Lastly, this looks to be a problem with Intel drivers, not even an MS bug.
So to turn it around, if you were MS would you hold back on your product launch because Intel had messed up when it isn't even a fatal problem to the machine, has a fairly easy low risk workaround, and you have no control over when Intel will release fixed drivers? It sounds to me like it hasn't fallen through any cracks, at least not at Microsoft, they just don't rate the bug as enough to block release just block to affected machines.
My i7 company laptop is the only machine here so far to update itself with this release, which went fine. Others are pretending they can't see an update, I would love to know why they are ignoring it.
We come back to the shady practice of mandatory feature updates and the associated enforced obsolescence. Whether Microsoft intend to break previously functioning systems or not, that is what the feature updates are doing. With automatic updates now de-rigueur, software developers are literally fighting over 'our' machines and blaming each other for the ensuing breakage.Quote:
Originally Posted by DanceswithUnix
Every time there is a major feature update we clear the decks in the workshop and prepare to be overloaded. Considering the 1000s of Windows PCs in our catchment, it's only ever a small percentage. Out of the mixed dozen of our own PCs, I've had one issue with one update; 1903 rendered one of my UHD monitors no better than FHD and has never been resolved.Quote:
My i7 company laptop is the only machine here so far to update itself with this release, which went fine. Others are pretending they can't see an update, I would love to know why they are ignoring it.
How many is too many? For those having to pay to get their systems repaired, the answer is probably just the one.
Microsoft started staging the big updates to avoid the patch Tuesday hell some time ago. Microsoft are aware of a clash between certain hardware and the the latest 2004 update (IIRC Nvidia are in the list) although there is typically an incompatibility warning. 'Golly gee your PC isn't quite ready for our latest and greatest but we will shoe horn it on just as soon as we can.' Sort of thing.
It is a tricky balance. Back in my embedded OS writing days I used to analyse some of the boxes that came back bricked after an update (because unbricking involved sending a man in a van with a replacement unit which cost us money). Most came down to things like filesystem corruption, so it wasn't the OS update per se that killed the machine it was just that any large activity was going to push it over the edge, and a OS update is as large an activity as those boxes ever performed.Quote:
Originally Posted by matts-uk
Ever since they changed the audio interface layout it has caused issues with my system,so they probably have mucked around with something underneath that. So I end up with no sound in games,or corruption of the sound drivers,causing some games to have other issues. So,I now repeatedly have to re-install the sound drivers after each Update to make sure its fine. This affected my older system,which was replaced by this newer system,which has one of the modern sound codecs.
This. I work for a software company, and we produce software that's very complicated with a lot of moving pieces. We have a large userbase. It's impossible to test every user workflow on every conceivable hardware/software configuration, and bugs are inevitable. It's also inevitable, given the need to drive development of new features and a finite development team, that some of those bugs will not be fixed. So yes, I understand MS's problem.Quote:
Originally Posted by DanceswithUnix
Intel has shared a fix for the Optane error message, as well as an explanation of what is happening.
https://www.intel.com/content/www/us...d-storage.html
Sounds like the root cause was Intel, not MS.Quote:
Originally Posted by Tabbykatze
I saw this error after updating my main box to 2004. I tried reinstalling the RST drivers - and it went away without any further ado.
Have to say that so far, there is zero downside to the new Windows build. Credit where it's due.
So the new Windows 10 update is unoptanable for certain people...? ;)
Sorry, I'll get my coat.