WINDOWS 10 1809 ISO RELEASE DATE UPDATE
And then I’m going to double-check what the real-world risk is to an individual user like me that no one (that I know of!) has any reason to target.Īnyway, I welcome any tips or corrections. Microsoft on Tuesday rereleased the Windows 10 October 2018 Update (version 1809), as well as Windows Server 2019 and its Windows Server-as-a-service cousins. We’re expecting Microsoft to show off Windows 11 on June 24. The current (*apparent*) need to assemble information from a variety of sources is too much work, even for people who know where to look.Īs for whether and when I might apply the current update, I’m probably going to wait for an update to InSpectre and then double-check its take on how performance might be affected. Version 1607 will be supported through October 13, 2026, and version 1809 until January 9, 2029.
It should be provided by Microsoft, but if they don’t do it, someone else should. Unless I’m being really stupid and overlooking something obvious, there needs to be a single utility that pulls in all of the requisite CPU/Platform/Microcode information and presents it in the same format used by Microsoft in its tables. €¢ GRC’s InSpectre utility returned a CPU ID in the same format used by Microsoft — HWInfo64 prepended leading zeroes to it — as well as the current microcode revision (which I didn’t spot anywhere else, though I may have been careless). €¢ HWInfo64 doesn’t provide all of it either, and you have to hunt down and identify the bits that *are* provided.
WINDOWS 10 1809 ISO RELEASE DATE SOFTWARE DOWNLOAD
Today we are resuming the rollout of the latest Windows 10 feature updateWindows 10, version 1809via the Software Download Center (via Update Assistant or the Media Creation Tool), Windows Server Update Services (WSUS), and Windows Update for Business. €¢ CPU-Z doesn’t seem to provide much the info needed. Windows 10, version 1809 rollout resumes now available on VLSC. €¢ Once I had the CPU’s full name (easily found in Settings>System), Intel’s page at provided a “Device ID” that didn’t match the format used in the table. €¢ Windows’ built-in GUI features (Settings>System>About and Device Manager>Processors) don’t seem to provide the requisite information. I am officially bitching about how hard it is to use the tables provided in Microsoft’s microcode update pages to determine whether the update is applicable to a given system.
0 kommentar(er)
