Skip to content
This repository has been archived by the owner on Feb 28, 2021. It is now read-only.

Latest Flash not returning server updates #51

Closed
Fonta opened this issue Jul 29, 2019 · 5 comments
Closed

Latest Flash not returning server updates #51

Fonta opened this issue Jul 29, 2019 · 5 comments
Assignees
Labels
bug Something isn't working

Comments

@Fonta
Copy link
Contributor

Fonta commented Jul 29, 2019

Hi Aaron,

Something seems to be off with Get-LatestAdobeFlashUpdate. No matter which arguments I provide, it doesn't seem to return the latest flash update for Windows Server 2016/2019.

Here it doesn't return the latest flash update for Windows Server 2019.

image

It also seems to return duplicate entries for build 1607 and also here the update for Server 2016 is missing.

image

@Fonta Fonta changed the title Latest Flash not returning Server 2019 update Latest Flash not returning Server updates Jul 29, 2019
@Fonta Fonta changed the title Latest Flash not returning Server updates Latest Flash not returning server updates Jul 29, 2019
@aaronparker aaronparker self-assigned this Jul 29, 2019
@aaronparker aaronparker added the bug Something isn't working label Jul 29, 2019
@aaronparker
Copy link
Owner

aaronparker commented Aug 3, 2019

If you run this with -Verbose, you'll see that it builds a search query for the Catalog: https://www.catalog.update.microsoft.com/Search.aspx?q=KB4503308+1809. From the feed this is the latest update. The catalog doesn't return any updates with Windows Server 2019 in the title.

Even a search for "adobe flash 1809" doesn't return Windows Server 2019 updates either. Searching for "2016" or "2019" does return updates.

Windows 10 x64 updates are applicable to Windows Server 2019 of course. I don't really want to add code just for 2016/2019 when the Windows 10 x64 updates apply.

@aaronparker aaronparker removed the bug Something isn't working label Aug 3, 2019
@Fonta
Copy link
Contributor Author

Fonta commented Aug 3, 2019

It does return results with "Windows Server 2019" in the name:
image

Also searching for the latest KB returns the windows server 2016/2019 etc wanted results:
image

Before your changes, it did return these results. So currently the function is returning incomplete/incorrect results.
Using it like -OS Windows10 -Version 1809 does not return the wanted results anymore.

@Fonta
Copy link
Contributor Author

Fonta commented Aug 24, 2019

Thanks for merging my PR. I was just thinking that it might be an idea to make the default fallback on PSCore to webclient as downloading is faster than using WebRequest as you can see in the screenshot underneath:
image

Also in Powershell 5, the difference is a lot bigger:
image

These test result are produced by the following small script: https://pastebin.com/0iksKb0w

@aaronparker aaronparker added the bug Something isn't working label Aug 25, 2019
@aaronparker
Copy link
Owner

I might look at using WebClient the default for all requests in the release after next. Querying the catalog could be faster and WebClient might help.

@aaronparker aaronparker mentioned this issue Aug 25, 2019
9 tasks
@Fonta
Copy link
Contributor Author

Fonta commented Aug 25, 2019

That would be best I guess. Would also help with implementing proxy support.

aaronparker added a commit that referenced this issue Aug 25, 2019
@Fonta Fonta closed this as completed Aug 31, 2019
@aaronparker aaronparker added this to In progress in LatestUpdate v3 Nov 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
LatestUpdate v3
  
In progress
Development

No branches or pull requests

2 participants