This blog posting represents the views of the author, David Fosberry. Those opinions may change over time. They do not constitute an expert legal or financial opinion.
If you have comments on this blog posting, please email me .
The Opinion Blog is organised by threads, so each post is identified by a thread number ("Major" index) and a post number ("Minor" index). If you want to view the index of blogs, click here to download it as an Excel spreadsheet.
Click here to see the whole Opinion Blog.
To view, save, share or refer to a particular blog post, use the link in that post (below/right, where it says "Show only this post").
Posted on 12th November 2024 |
Show only this post Show all posts in this thread (Software). |
|
This report on Tom's Hardware describes a recent buggy update to Microsoft's server software. The update in question shouldn't concern normal home users, since it is for users of Windows Server 2022. Corporate users of Microsoft products have better control of which updates are installed, and when, so do not usually suffer the same surprises as private users. Typically, system administrators will configure their systems to automatically install security updates immediately, and schedule other updates and upgrades when convenient. This update, however, was labelled as a security update, when in fact it upgraded systems from Windows Server 2022 to Windows Server 2025. The biggest problem with this upgrade is that it is a new product, requiring new licences, so that customers will have to pay for the new licences which they didn't ask for. All this demonstrates once again that Microsoft:
| |