If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Rate Thread | Display Modes |
#1
|
|||
|
|||
Is my computer up-to-date?
Winver says,
Version 1903 (OS Build 18362.356) |
Ads |
#2
|
|||
|
|||
Is my computer up-to-date?
Alek wrote:
Winver says, Version 1903 (OS Build 18362.356) If that is what Microsoft's WSUS servers have offered you then, yep, you are up to date. I'm current at 1903 build 18362.295; however, I haven't allowed a reboot to allow the update to install (I rescheduled for next Tuesday, or I might do it sooner after saving an image backup). The pending update is for KB4515384: https://support.microsoft.com/en-us/...date-kb4515384 I think it's a reissue (i.e., another version of same update). It is still causing Start menu problems even in its reincarnation. https://www.windowscentral.com/micro...date-kb4515384 https://docs.microsoft.com/en-us/win...903#688msgdesc According to the MS KB article, that update changes the Windows version to "OS Build 18362.356", so you already have KB4515384 installed, and hopefully aren't encountering the severe nasties that it can inflict. |
#3
|
|||
|
|||
Is my computer up-to-date?
VanguardLH wrote:
According to the MS KB article, that update changes the Windows version to "OS Build 18362.356", so you already have KB4515384 installed, and hopefully aren't encountering the severe nasties that it can inflict. If your mean Cortana going postal chewing up CPU even when you have Cortana disabled then, yep it hit me! The fix for me was the registry edit. Computer\HKEY_CURRENT_USER\Software\Microsoft\Wind ows\CurrentVersion\Search\BingSearchEnabled I had to temporary switch from 0 to 1 and reboot. I'll switch it back after they patch this patch... -- Take care, Jonathan ------------------- LITTLE WORKS STUDIO http://www.LittleWorksStudio.com |
#4
|
|||
|
|||
Is my computer up-to-date?
"Jonathan N. Little" wrote:
VanguardLH wrote: According to the MS KB article, that update changes the Windows version to "OS Build 18362.356", so you already have KB4515384 installed, and hopefully aren't encountering the severe nasties that it can inflict. If your mean Cortana going postal chewing up CPU even when you have Cortana disabled then, yep it hit me! The fix for me was the registry edit. Computer\HKEY_CURRENT_USER\Software\Microsoft\Wind ows\CurrentVersion\Search\BingSearchEnabled I had to temporary switch from 0 to 1 and reboot. I'll switch it back after they patch this patch... Except that registry hack isn't working in the reincarnation of KB4515384. If you were susceptible to the nasties that it inflicted before, the registry hack to fix one of them doesn't work in the latest version of the update. From the WindowsCentral article to which I linked in my prior reply: "While there's a chance that it is related to the bug on build 18362.329, enabling the "BingSearchEnabled" Registry key won't resolve the issue." |
#5
|
|||
|
|||
Is my computer up-to-date?
VanguardLH wrote:
"Jonathan N. Little" wrote: VanguardLH wrote: According to the MS KB article, that update changes the Windows version to "OS Build 18362.356", so you already have KB4515384 installed, and hopefully aren't encountering the severe nasties that it can inflict. If your mean Cortana going postal chewing up CPU even when you have Cortana disabled then, yep it hit me! The fix for me was the registry edit. Computer\HKEY_CURRENT_USER\Software\Microsoft\Wind ows\CurrentVersion\Search\BingSearchEnabled I had to temporary switch from 0 to 1 and reboot. I'll switch it back after they patch this patch... Except that registry hack isn't working in the reincarnation of KB4515384. If you were susceptible to the nasties that it inflicted before, the registry hack to fix one of them doesn't work in the latest version of the update. From the WindowsCentral article to which I linked in my prior reply: "While there's a chance that it is related to the bug on build 18362.329, enabling the "BingSearchEnabled" Registry key won't resolve the issue." Except KB4515384 was the update that first cause my issue. The registry hack did resolve it. If they reissue the patch with "fixes" they would not use the same KB# -- Take care, Jonathan ------------------- LITTLE WORKS STUDIO http://www.LittleWorksStudio.com |
#6
|
|||
|
|||
Is my computer up-to-date?
Jonathan N. Little wrote:
VanguardLH wrote: "Jonathan N. Little" wrote: VanguardLH wrote: According to the MS KB article, that update changes the Windows version to "OS Build 18362.356", so you already have KB4515384 installed, and hopefully aren't encountering the severe nasties that it can inflict. If your mean Cortana going postal chewing up CPU even when you have Cortana disabled then, yep it hit me! The fix for me was the registry edit. Computer\HKEY_CURRENT_USER\Software\Microsoft\Wind ows\CurrentVersion\Search\BingSearchEnabled I had to temporary switch from 0 to 1 and reboot. I'll switch it back after they patch this patch... Except that registry hack isn't working in the reincarnation of KB4515384. If you were susceptible to the nasties that it inflicted before, the registry hack to fix one of them doesn't work in the latest version of the update. From the WindowsCentral article to which I linked in my prior reply: "While there's a chance that it is related to the bug on build 18362.329, enabling the "BingSearchEnabled" Registry key won't resolve the issue." Except KB4515384 was the update that first cause my issue. The registry hack did resolve it. If they reissue the patch with "fixes" they would not use the same KB# They can. Each KB has versioning. That's why the recurring "monthly scan" thing, the MSRT, uses the same KB number each time it is installed. Since it is versioned, the new one supercedes the old one, and uses the same KB. Since I am a collector of junk, I have a couple random samples in my Downloads folder. These are compressed 40MB files that expand to MSRT.exe 100MB or so. windows-kb890830-x64-v5.66_324d7f131dd4bd5ede96c9526a81970efeaa9d4e.exe windows-kb890830-x64-v5.71_2082573da8820621dd2f2393dcf185ceb5410d31.exe A number of KBs have "double installed", and I've never seen a description of exactly why two are needed for them to "take". Because they can come in, immediately, one after the other. The second instance of the update, seems to be a shorter download. And even though those files in the example, have the "v5.66" thing, I think that is not the controlling number, and the enumeration follows some other pattern and field. For example, the version.txt file inside those EXEs, doesn't follow any known pattern. They're versioned, but I can't confirm any particular method as being the "important one". You might have to take apart the wsusscn2 cab file to be sure. It's around 500MB or so now (has all the OSes in it). Lots of operations on Windows Update, use small sections of that. (The Microsoft Baseline Security Analyzer, which doesn't work particularly for Windows 10, downloads the whole wsusscn2 file.) It's because of versioning, you can't use any blocking mechanism to stop them from coming in. You could tell the system to stop accepting 890830 V5.66 and then v5.71 would come in and cause the same nuisance again. The mechanism isn't smart enough to do "890830 *" and wild-card the version. Paul |
#7
|
|||
|
|||
Is my computer up-to-date?
In message , Paul
writes: [] It's because of versioning, you can't use any blocking mechanism to stop them from coming in. You could tell the system to stop accepting 890830 V5.66 and then v5.71 would come in and cause the same nuisance again. The mechanism isn't smart enough to do "890830 *" and wild-card the version. Paul Has anyone ever asked Microsoft why this is, and (I'm sure people have) if so, has any comprehensible answer ever been forthcoming? Being able to stop a KB, because you know it causes a specific problem, is surely a valid desire, at least where the facility is offered. (I guess the question will become moot after January, as I don't think the option-to-stop - without third party software - is available in 10?) -- J. P. Gilliver. UMRA: 1960/1985 MB++G()AL-IS-Ch++(p)Ar@T+H+Sh0!:`)DNAf A lot of people think that being skinny is the happy ending, and its not. Being happy is the happy ending. - Sarah Millican, in Radio Times 3-9 March 2012 |
#8
|
|||
|
|||
Is my computer up-to-date?
"Jonathan N. Little" wrote:
If they reissue the patch with "fixes" they would not use the same KB# YES THEY DO!!! Updates can get revised and come out AGAIN under the same KB number. That is why you can elect to hide an update (back in Windows XP/7/8) but it could come back to get offered again. When you hid an update, you only got to hide THAT version of the update. When Microsoft pushed out a new version of it, the hide was ineffective, so you got to see the new version offered to you, and you had to hide it again. This is how, for example, Microsoft managed to keep pushing the GWX (Get Windows 10) "update" that tried to get users to upgrade to Windows 10. Users that didn't want to move away from their existing but old version of Windows would hide that update. Microsoft came out with a new version and, yep, it would show up as another "new" update. That's why someone came up with a monitor that would watch for the reappearance of the GWX update under a new version to block it (GWX Control Panel, https://www.majorgeeks.com/files/det...ol_panel.html). You'd disconnect the doorbell to avoid a salesman, but the salesman would change his clothes, grow a mustache, rewire your doorbell, and bother you again with his "new" products that were the same as the old ones but now with a different look (you know, "new and improved" which meant the stuff you were using is now "old and crap"). Improved doesn't mandate correctly fixed, just slightly changed code. Updates do get a version assigned. When "fixed", they get a new version. Each time there is a new version, you get offered the new version of the modified update and under the same KB number. You see the same KB number get offered again. An update with a new version means there have been changes to the update (aka fixes trying to correct problems not wholly addressed or created new in the prior version). |
#9
|
|||
|
|||
Is my computer up-to-date?
VanguardLH wrote:
"Jonathan N. Little" wrote: If they reissue the patch with "fixes" they would not use the same KB# YES THEY DO!!! Updates can get revised and come out AGAIN under the same KB number. That is why you can elect to hide an update (back in Windows XP/7/8) but it could come back to get offered again. When you hid an update, you only got to hide THAT version of the update. When Microsoft pushed out a new version of it, the hide was ineffective, so you got to see the new version offered to you, and you had to hide it again. This is how, for example, Microsoft managed to keep pushing the GWX (Get Windows 10) "update" that tried to get users to upgrade to Windows 10. Users that didn't want to move away from their existing but old version of Windows would hide that update. Microsoft came out with a new version and, yep, it would show up as another "new" update. That's why someone came up with a monitor that would watch for the reappearance of the GWX update under a new version to block it (GWX Control Panel, https://www.majorgeeks.com/files/det...ol_panel.html). You'd disconnect the doorbell to avoid a salesman, but the salesman would change his clothes, grow a mustache, rewire your doorbell, and bother you again with his "new" products that were the same as the old ones but now with a different look (you know, "new and improved" which meant the stuff you were using is now "old and crap"). Improved doesn't mandate correctly fixed, just slightly changed code. Updates do get a version assigned. When "fixed", they get a new version. Each time there is a new version, you get offered the new version of the modified update and under the same KB number. You see the same KB number get offered again. An update with a new version means there have been changes to the update (aka fixes trying to correct problems not wholly addressed or created new in the prior version). shakes head Microsoft's concept of version control...ugh. This is way this is my only device left running Windows. And most likely my last. -- Take care, Jonathan ------------------- LITTLE WORKS STUDIO http://www.LittleWorksStudio.com |
#10
|
|||
|
|||
Is my computer up-to-date?
"Jonathan N. Little" wrote:
VanguardLH wrote: "Jonathan N. Little" wrote: If they reissue the patch with "fixes" they would not use the same KB# YES THEY DO!!! Updates can get revised and come out AGAIN under the same KB number. That is why you can elect to hide an update (back in Windows XP/7/8) but it could come back to get offered again. When you hid an update, you only got to hide THAT version of the update. When Microsoft pushed out a new version of it, the hide was ineffective, so you got to see the new version offered to you, and you had to hide it again. This is how, for example, Microsoft managed to keep pushing the GWX (Get Windows 10) "update" that tried to get users to upgrade to Windows 10. Users that didn't want to move away from their existing but old version of Windows would hide that update. Microsoft came out with a new version and, yep, it would show up as another "new" update. That's why someone came up with a monitor that would watch for the reappearance of the GWX update under a new version to block it (GWX Control Panel, https://www.majorgeeks.com/files/det...ol_panel.html). You'd disconnect the doorbell to avoid a salesman, but the salesman would change his clothes, grow a mustache, rewire your doorbell, and bother you again with his "new" products that were the same as the old ones but now with a different look (you know, "new and improved" which meant the stuff you were using is now "old and crap"). Improved doesn't mandate correctly fixed, just slightly changed code. Updates do get a version assigned. When "fixed", they get a new version. Each time there is a new version, you get offered the new version of the modified update and under the same KB number. You see the same KB number get offered again. An update with a new version means there have been changes to the update (aka fixes trying to correct problems not wholly addressed or created new in the prior version). shakes head Microsoft's concept of version control...ugh. This is way this is my only device left running Windows. And most likely my last. And the software you install has versioning, as do the drivers you install, and everything else that is SOFTware. Even hardware has versioning but it doesn't change until replaced unless it has reprogrammable firmware. |
Thread Tools | |
Display Modes | Rate This Thread |
|
|