That's because you probably manually installed the CU, normally the SSU (KB4058702) is a companion update for the CU when installed by WU, it won't be shown in Update History anyway, only at "Installed updates". If it isn't there install it manually.
What do you think guys ? Will they release an updated iso with the spectre/metldown patch included or considering they just released one in december they will wait a few months ?
The next official 16299.xxx release will be next jan. 22. 2018, in february/march rs4 will be released. https://forums.mydigitallife.net/th...9-64-16299-125-pc.75255/page-149#post-1403392 MSFT is still working with AMD to solve the AMD related problems, progress is expected next week.
Was wondering where the 17025 build that appeared in UUP was from : Code: 17:46:12 INSIDER SLOW ACTIVE QUERY 17:46:12 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 17:46:14 Build NR: 17025.1000 17:46:14 Architecture: amd64 17:46:14 UUP ID NR: 3a2c6f42-9dd3-40ea-954c-ad8b0dfaa4b0 17:46:14 Release Name: Windows 10 Insider Preview 17025.1000 (rs_prerelease) 17:46:14 Database Check: NO_SAVE 17:46:14 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 17:46:17 Build NR: 16299.125 17:46:17 Architecture: x86 17:46:17 UUP ID NR: 2dba42e9-a4ce-4736-a22e-dc2daa247dd0 17:46:17 Release Name: Feature update to Windows 10, version 1709 (16299.125) 17:46:17 Database Check: NO_SAVE 17:46:17 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 17:46:26 Build NR: 16299.125 17:46:26 Architecture: arm64 17:46:26 UUP ID NR: 87d62dde-f2a8-4833-86d6-cfa7325a674b 17:46:26 Release Name: Feature update to Windows 10, version 1709 (16299.125) 17:46:26 Database Check: NO_SAVE 17:46:26 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
So I checked Windows Update on my brother's PC and it displays "device is up to date." I checked "winver" and it reports system as build 16299.19 (which came out October 17, 2017). It's Windows 10 x64 Enterprise, i7 4790K with Windows Defender ON and I confirmed the registry key is present and enabled to receive further updates after January 2018. Why is WU so dumb? At the very least why not simply report the system is NOT up to date - that's all I ask - and leave me with the work of manually downloading the update. Why does it lie? WHY? Do I have to make a batch file that runs on startup that opens "winver" and the browser page to Microsoft's own Windows Update history to see the current Windows version?
That solved the problem of my friend as well, he had some entries related to Microsoft in Hosts file as well. Deleted them and now 16299.192 appeared on WU. @2574 If you have those entries on Hosts file, that's the problem why it isn't showing on WU.
Not dumb actually but checking for a lot of stuff to ensure compatibility. Is that an AMD system your brother has?
It's not logical for a system to report to the user that it is up to date, when it is clearly not. Where is the simple string comparison function? Is this modern computer now HAL9000? Hal, is my computer up to date? Yes Dave, it's up to date.
Yes, it's there! Thank you! So, anyone, if you have an issue about not being able to install Meltdown and Spectre updates via WU, do clear your Telemetry adjustments (Hosts file and Win Firewall rules were mine). I guess, reverting them back -to no spying by MS- is fine now?
Is telemetry set to 0 ? you expect WU to report "not up to date" without offering the up to date updates? WU works on metadata and applicability rules it's not just simple comparison
Yes you're right but when I set this setting a long time ago I did not realize it would affect windows updates. I thought it would at least give me security updates. edit: pounding out the above post I did not see you had posted before i hit post
Any new info on what is new in WDDM 2.3 and whether it includes DXGI 1.7? Are there any services or tweaks that work without problems in Pre-1709 builds that cause major issues (like network) on 1709+ builds?
I dont know if this is the right place to ask, but please tell me what is this "MVS ISO" meant by? Can i use this to do a fresh install? What is the difference between "MVS iso" & "RTM iso from msdn." Also, "Official 16299.125 MVS iso" - is this iso created from .esd or UUP files?
@YED MVS stands for MyVisualStudio. ISO downloaded from MVS are officially provided by Microsoft and later distributed everywhere. Like one would say 'straight from the horse's mouth'. Obviously, you can use it for clean install. There are no MSDN or VLSC now. They are all migrated to MVS portal. As far as your final question is concerned, it looks like official ISO and not the one created from UUP or ESD. If you can share checksum of that ISO, then one would be able to help you. Just to add a little more, ISO created from ESD and UUP are also official but checksums can be different, contents will be all the same.
Thx for the replay bro. Official 16299.125 MVS ISOs by @LostED - this is what i was asking. But now i understand completely. Thank for u r help
hmm my corntana search is show white(even I'm not use search for example).. it just appeared in 16299.125 even update 16299.192 it maybe cortana it not avaible? location and languange setting is en-us.. strange anyone experienced that?