PowerShell GUI for Downloading Microsoft Store Apps - W10_11StoreApps.ps1

Like you, I have seen weird discrepancies to what rg-adguard reports as the "latest version". My suspicion is they're doing some caching on their end, so they're not always returning the latest product build.
Some of that is Microsoft file labeling. I have found more than one app whose file name version number differs from the version number found inside the archive. You sometimes have to look inside the archive at the AppxManifest.xml to know what version the program truly is.
 
Try this beta build. There's a new checkbox to include 32-bit versions of dependencies, if they exist.

A variable at the script's start controls whether this checkbox is auto-checked or not. You can change it to your preferred default.
Code:
$Include32bit_Preference = $true

View attachment 15461


I don't know if this happened with the old version, but this version downloads the dependencies even if I don't have the box checked.
 
The normal script only downloads dependencies that match your specific architecture (x64 or x86).

Diatomacious' request was to include both sets of files if you're running on a 64-bit platform, as a convenience for the user (since the script's already doing the work). I don't want to make the checkbox the default for everyone, because some users have complained in the past they don't want the extra packages.
 
The normal script only downloads dependencies that match your specific architecture (x64 or x86).

Diatomacious' request was to include both sets of files if you're running on a 64-bit platform, as a convenience for the user (since the script's already doing the work). I don't want to make the checkbox the default for everyone, because some users have complained in the past they don't want the extra packages.

Just to be clear, this is what I was talking about. They are both unchecked, but the x64 dependencies are downloaded anyway.
 

Attachments

  • Screenshot_3.png
    Screenshot_3.png
    25.7 KB
Hello,
is there any changes I am getting from today always "The remote server returned an error: (403) Forbidden." for ps1 script
 
I'm getting the same error.

http://store.rg-adguard.net appears to be having network issues. Browsing the web form (where I'm sending the search request) is returning "Bad gateway 502" errors. I suspect it's down on their back-end. Maybe wait a few hours until they restore service.

The Store API on MS side is not returning any errors.
 
After more debugging, rg-adguard is now enforcing a browser check in the search request.

I'm not sure why they suddenly decided to limit requests, unless lots of other tools are piggybacking off their search results. I have a direct API version of this script, so I'm not worried about getting locked out.

Please download the updated script from post #1.
 
No, over the years I've found a number of other tools that piggyback off rg-adguard. You can find them on GitHub.
 
Back
Top