Jan 29 2020 KB pathes for Win 10 rolled back my kernel verison

%3CLINGO-SUB%20id%3D%22lingo-sub-1139769%22%20slang%3D%22en-US%22%3EJan%2029%202020%20KB%20pathes%20for%20Win%2010%20rolled%20back%20my%20kernel%20verison%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1139769%22%20slang%3D%22en-US%22%3E%3CP%3EOn%20my%20windows%2010%2064%20bit%20enterprise%201909%20PC's%20I%20applied%20the%20two%20patches%20KB4534132%20and%20KB%204532695%20yesterday%20afternoon%2029th%20Jan%202020.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENessus%26nbsp%3B%20on%20KALI%20scan%20before%20patch%20did%20not%20show%20this%20issue.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%20when%20I%20run%20today's%20Ness's%20update%20scans%20it%20is%20reporting%20that%20c%3A%5Cwindows%5Csystem32%5Cntoskrnl.exe%20as%20out%20of%20date.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESure%20enough%20the%20ntoskrnl.exe%20file%20was%20updated%20on%2029th%20Jan%202020%20and%20is%20now%20at%20version%2010.0.18362.628%20when%20it%20should%20be%20at%20version%2010.0.18363.535%20due%20to%20KB434868%20installed%20in%20December%202019!!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAnyone%20else%20having%20this%20issue%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHCG%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1147859%22%20slang%3D%22fr-FR%22%3ERe%3A%20Jan%2029%202020%20KB%20pathes%20for%20Win%2010%20rolled%20back%20my%20kernel%20verison%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1147859%22%20slang%3D%22fr-FR%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F258685%22%20target%3D%22_blank%22%3E%40skehana%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHello%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESame%20version%2010.0.18362.628%20on%20my%20PC%20latest%20with%20updates.%3C%2FP%3E%3CP%3EBest%20looks.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1151759%22%20slang%3D%22en-US%22%3ERe%3A%20Jan%2029%202020%20KB%20pathes%20for%20Win%2010%20rolled%20back%20my%20kernel%20verison%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1151759%22%20slang%3D%22en-US%22%3EThere%20are%20no%20files%20exist%20with%20version%2018363%2C%20it's%20registry%20only%20version%20to%20distinguish%201909%20and%201903%3CBR%20%2F%3Eall%20files%20in%20both%20are%2018362%3C%2FLINGO-BODY%3E
New Contributor

On my windows 10 64 bit enterprise 1909 PC's I applied the two patches KB4534132 and KB 4532695 yesterday afternoon 29th Jan 2020.

 

Nessus  on KALI scan before patch did not show this issue.

 

Now when I run today's Ness's update scans it is reporting that c:\windows\system32\ntoskrnl.exe as out of date.

 

Sure enough the ntoskrnl.exe file was updated on 29th Jan 2020 and is now at version 10.0.18362.628 when it should be at version 10.0.18363.535 due to KB434868 installed in December 2019!!

 

Anyone else having this issue?

 

HCG

2 Replies

@skehana 

Hello,

 

Same version 10.0.18362.628 on my PC with latest updates.

Best regards.

There are no files exist with version 18363, it's registry only version to distinguish 1909 and 1903
all files in both are 18362