Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

False Positive #19

Closed
MatsBEkman opened this issue Mar 7, 2019 · 14 comments
Closed

False Positive #19

MatsBEkman opened this issue Mar 7, 2019 · 14 comments

Comments

@MatsBEkman
Copy link

https://file.io/8uY2uI
Regards
Mats

@bitsadmin
Copy link
Owner

Thanks Mats. Can you check the link? It shows a 404 for me.

@bitsadmin
Copy link
Owner

Hi Mats, please also check out the Eliminating false positives page on the Wiki. In case that does not drastically reduce the number of false positives, share the link with your outputs.

@MatsBEkman
Copy link
Author

file.io don't work for me I attach file here
wesupdate_2019-03-07.zip

@MatsBEkman
Copy link
Author

Also try this
https://file.io/NzjORR
I think I found out the problem
When I test it goes away 1 Download only

@MatsBEkman
Copy link
Author

Running again with 0.94
https://file.io/S8zUVY
Eliminated the problem by investigating the different KBs and running with
wes.py systeminfo.txt -p KB4487044 KB4483452 KB4477029 KB4480979
I don't know if this is the correct procedure but it seems to me that Your source is not reliable when it comes to substitutions

@bitsadmin
Copy link
Owner

Hi Mats, thanks for your checks!

I also did some investigation and added your case as an example to the Wiki: https://github.com/bitsadmin/wesng/wiki/Eliminating-false-positives#example-2-mats

The main problem indeed is that the official source (MSRC, see the Developers page at the wiki for more info), is frequently missing information about supersedence. In my experience the Microsoft Update Catalog usually contains the correct information, so a manual check needs to be performed on the output of wes.

As far as I know the Microsoft Update Catalog does not provide an API to obtain all information about supersedence which could be used to complement (or even replace) MSRC.

Just curious, does your system allow the installation of KB4483452 if you manually download it from the Microsoft Update Catalog? Url: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4483452

@MatsBEkman
Copy link
Author

MatsBEkman commented Mar 8, 2019 via email

@MatsBEkman
Copy link
Author

MatsBEkman commented Mar 8, 2019 via email

@bitsadmin
Copy link
Owner

I agree, I am also not exactly sure about this remaining patch. The Windows Update tool on your machine is the definite answer: in case Windows Update does not list any remaining updates, your system must be fine and the data in the Windows Update Catalog website is incomplete.

@MatsBEkman
Copy link
Author

MatsBEkman commented Mar 10, 2019 via email

@bitsadmin
Copy link
Owner

I guess the update is indeed too recent or so. Don't think we can do much about these issues if the latest data is still incomplete. Thanks for your input! Let's close this issue for now, and if you run into other unexpected behavior, feel free to open an new issue!

@MatsBEkman
Copy link
Author

MatsBEkman commented Mar 11, 2019 via email

@bitsadmin
Copy link
Owner

Ah interesting usage of the tool, hadn't thought of that usecase yet :)

If you want to perform this evaluation on a server park, it should be possible to collect the information from many servers using the Get-ComputerInfo PowerShell command (once implemented) and then use wes.py to evaluate if they are missing any patching. You can output the results to csv to generate nice statistics based on that.

@MatsBEkman
Copy link
Author

MatsBEkman commented Mar 13, 2019 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants