Subject: Re: Figure out Windows build scheme, possibly from scratch :-P ( #53) The downside being that you’ll be left without those security measures brought in by KB5027215, of course.To: vegastrike/Vega-Strike-Engine-Source Hopefully Microsoft will investigate the issues flagged here, and any necessary fixes can be applied in a timely manner. So, this is still an issue Microsoft (indirectly) caused.Īt any rate, the hints of serious trouble around KB5027215 may lead the cautious to pause this update for the time being, and that could be a wise decision. (It was not an update piped directly from Dell). That said, the blame for pushing the new firmware directly to the laptop can be laid at the feet of Windows Update, which really shouldn’t be running that kind of firmware update automatically, in the background, without the user knowing. So, while the initial reaction was to rage at the update – unsurprisingly – after investigation, KB5027215 was innocent here. In actual fact, it was a Dell firmware update pushed alongside patch KB5027215 which messed up the notebook’s charging functionality. To illustrate this, in the above linked Reddit thread, there’s a complaint of a Windows 10 laptop going wonky post-update, with its charger no longer recognized, but it turns out that the cumulative update wasn’t to blame in this case. We must be careful about how much we read into reports of bricking devices, of course, when they are scattered findings.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |