unknown2304

UUP dump app essay

Sep 14th, 2023 (edited)
1,989
1
188 days
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 11.08 KB | Software | 1 0
  1. UUP dump app
  2.  
  3. "UUP dump app" is a UUP dump project that runs locally on your machine
  4. You can get any build with it, but very old builds are dead on the MSFT side and it's not possible to get those builds even with an older database archive
  5. UUP dump Discord server: https://discord.gg/yVRbtb2
  6.  
  7. The "website" code is located in the "uup-dump" folder
  8. The "website" config file location is "uup-dump\config.ini"
  9. The "JSON API" code is located in the "uup-dump\json-api" folder
  10. The "UUP dump API" code is located in the "uup-dump\api" folder
  11. The very limited "standalone" copy is located in the "uup-dump\sta" folder
  12. The build database consists of "fileinfo" and "packs" folders inside the "uup-dump" folder
  13.  
  14. Some options in the "uup-dump\config.ini" config file:
  15. allow_corpnet - this option allows you to check internal non-downloadable builds, works only with the MSIT channel
  16. show_render_time - this option displays page rendering statistics in the lower left corner of the web page
  17. proxy - this option allows you to use HTTP proxy, for example: proxy=127.0.0.1:50555
  18.  
  19. You can move the "uupdump-get.cmd" and "uupdump-run.cmd" scripts to the root folder if you do not want to use the "uupdump-aio.cmd" script
  20.  
  21. In short, you should run the server with the prefered script and then add some builds to your database
  22.  
  23.  
  24. 1. How to run it
  25.  
  26. "UUP dump app" download links:
  27. https://mega.nz/folder/YoAFAY6S#YK8llN-X4wi3fyumy_Zbxw
  28. https://app.mediafire.com/r2j3lzhhghsv6
  29. https://pixeldrain.com/l/zHAzrL4G
  30.  
  31. Download and extract the "uupdump-x64-v1.7.1-r7.7z" or "uupdump-x64-v1.7.1-r7.7z" archive to any folder without Unicode symbols in the path
  32. Then use the "uupdump-aio.cmd" or "scripts\uupdump-run.cmd" script to start the server. The Apache HTTP Server is much faster and more stable
  33. If for some reason you can't run the Apache HTTP Server, you could try the built-in PHP web server, but it is very slow and not reliable in a local network environment
  34.  
  35. Some scripts features won't work if there are Unicode symbols in the path to the UUP dump app, and this is a PHP problem
  36. x64 version is for 64-bit Windows OS only
  37. x86 version is for both 32-bit and 64-bit OS, on 64-bit systems it should be slower than the x64 version
  38.  
  39.  
  40. PHP and the Apache HTTP Server require Microsoft Visual C++ Redistributable Runtimes, you can get it from MSFT or use any reliable AIO Repack
  41.  
  42. MSFT links:
  43. https://aka.ms/vs/17/release/vc_redist.x86.exe
  44. https://aka.ms/vs/17/release/vc_redist.x64.exe
  45.  
  46. AIO Repack by abbodi1406:
  47. https://github.com/abbodi1406/vcredist
  48.  
  49. If you are having problems with VC++ Redist, try to remove it with the /aiR switch in the AIO Repack, then reinstall it
  50.  
  51.  
  52. You can edit the "uupdump-aio.cmd" and "uupdump-run.cmd" scripts options using Notepad++:
  53. serverrun - changes the local server start mode
  54. autorun - automatically launches the website in your default web browser
  55. uimode - switches website to Dark or Light mode on startup
  56. browser - changes the default web browser, also works with portable web browsers
  57.  
  58.  
  59. 2. How to automatically add the latest builds to your database
  60.  
  61. If you want to get the latest builds then just use the "uupdump-aio.cmd" or "scripts\uupdump-get.cmd" script. Run the "Start detecting new builds" option and wait ~10 minutes
  62. All data is from Windows Update, so your results may vary depending on the CDN and availability of the service in your area. Normally you should get ~40 build entries on the first few runs
  63.  
  64. Windows Insider program is banned in Russia / Belarus, use VPN to get around this restriction or you'll only get Retail builds
  65. If the Windows Update service is busy, just rerun the "Start detecting new builds" option several times, expect some errors in the log. Use VPN if you can't get it to work in your location
  66.  
  67. If Windows Update is blocked on your machine, you won't be able to get builds from MSFT into your database
  68. To get it to work you should check your host file (C:\Windows\System32\drivers\etc\hosts) and remove any MSFT related stuff
  69. If that doesn't help, check (or disable) your firewall, or try it on another machine
  70.  
  71. If you do not want to get builds for all architectures (x86, amd64, arm64) or for all channels (Retail, RP, Beta, Dev, Canary) then just change the script options
  72. The "MSIT {Internal Corpnet}" channel is excluded from the ALL channel by default
  73.  
  74.  
  75. You can edit these scripts and modify the detected builds, or enable autorun of the local server, etc.
  76.  
  77. Let's break down builds checker example in the "uupdump-get.cmd" script:
  78. call :dAll Retail "19044 1202 125"
  79.  
  80. :dAll - architecture, :dAll = x86, x64, arm64. You can find more values at the end of the script
  81. Retail - channel (or ring), some supported values: Retail, ReleasePreview, Beta, Dev, Canary, MSIT. Read more in the "UUP dump API" documentation
  82. 19044 - build version
  83. 1202 - Cumulative Update version (19044 1202 means build 19044.1202 if you don't get it)
  84. 125 - SKU, edition of the build (125 is the "Enterprise LTSC" edition)
  85.  
  86. Some SKU values:
  87. 101 - Home
  88. 48 - Pro
  89. 121 - Education
  90. 4 - Enterprise
  91. 72 - Enterprise Evaluation
  92. 125 - Enterprise LTSC
  93. 129 - Enterprise LTSC Evaluation
  94. 119 - Team
  95. 7 - Server Standard
  96. 8 - Server Datacenter
  97. 406 - Azure Stack HCI
  98. 407 - Server Datacenter Azure Edition
  99.  
  100.  
  101. As mentioned above, the build database consists of "fileinfo" and "packs" folders
  102. Simply speaking, the "fileinfo" data is builds and the "packs" data is Metadata for each build
  103. By default the "Start detecting new builds" option is getting both "fileinfo" and "packs" data
  104.  
  105. If you only need the new builds then disable the "Generate packs" option
  106. If you only need to generate metadata for all or manually added builds then go to the "Generate all packs" menu and run the "Start generating all packs" option
  107.  
  108.  
  109. 3. How to add the latest builds to your database manually
  110.  
  111. There are several ways to do this, the first of which is the "Quick Options" block on the website home page
  112. Just click on the any architecture button (x64, arm64 or all) next to your chosen channel and you should get the latest build in ~10 seconds
  113.  
  114. If you want to get a public Preview build on the "Retail" channel then you should check that build on the "Release Preview" channel instead
  115. "Quick Options" should work with any 22621+ client build, so if you want to get a Windows 10 build, this isn't your method
  116. You will need to generate metadata for your manually added builds: run the "uupdump-aio.cmd" or "scripts\uupdump-get.cmd" script and use the "Start generating all packs" option in the "Generate all packs" menu
  117.  
  118.  
  119. Another way to manually add the latest builds is to use the "+ New build" feature on the website. The logic is the same as in the "uupdump-aio.cmd" or "scripts\uupdump-get.cmd" scripts
  120. In most cases it's sufficient to check only base builds, for example: 19045.1, 22000.1, 22621.1, 22631.1 and so on
  121. You will still need to manually generate metadata for each added build. Again, run the "uupdump-aio.cmd" or "scripts\uupdump-get.cmd" script and use the "Start generating all packs" option in the "Generate all packs" menu
  122.  
  123.  
  124. 4. How to add any old build to your database manually
  125.  
  126. If you want to get any old build and do not have an archive of builds in your database, this section is for you
  127.  
  128. You can add any exact build on the "+ New build" page on the website with "thisonly" flag
  129. It is possible to edit the "uupdump-aio.cmd" or "scripts\uupdump-get.cmd" scripts and use it instead, but this is not an efficient way so let's focus on the "+ New build" page on the website
  130.  
  131. Example of manually adding build 22621.1848 on the "+ New build" page on the website:
  132. x64 / amd64 | Retail | 22621.1848+thisonly | Pro --> Next
  133.  
  134. Generate metadata for your added builds using the "Start generating all packs" script option
  135.  
  136.  
  137. 5. How to get a very large builds archive and add it to your database
  138.  
  139. The builds archive should be located in the same cloud folder as the UUP dump app
  140. Download and extract the archive file "Builds archive - Oct 19, 2023.7z" and move its contents to the "uup-dump" folder
  141. Warning: Archive is very heavy and takes about ~10 Gb. of space after extraction
  142.  
  143.  
  144. Alternatively you can run the "scripts\uupdump-download-archive-aria2.cmd" script which should download the latest builds data from Github using aria2
  145. Advanced users can use git to clone and update "fileinfo" and "packs" repos using the "scripts\uupdump-download-archive-git.cmd" script
  146.  
  147. Keep in mind that builds data on Github is not updated regularly, you can find the unofficial repos here:
  148. https://github.com/EverchangerL/fileinfo - UUP dump file information repository
  149. https://github.com/EverchangerL/packs - UUP dump packs repository
  150.  
  151.  
  152. 6. How to check non-downloadable internal builds
  153.  
  154. It's possible to check some internal builds with the UUP dump app. You can't download any internal build without MSFT VPN so this section is pointless
  155.  
  156. Easy way:
  157. Run the "uupdump-aio.cmd" or "scripts\uupdump-get.cmd" script, change "Channel" option to the "MSIT {Internal Corpnet}" and run the "Start detecting new builds" option
  158.  
  159.  
  160. Manual way:
  161. Edit the "uup-dump\config.ini" config file and enable the "allow_corpnet" option (allow_corpnet=true)
  162. After that use the "+ New build" feature on the website to check some builds with "corpnet" flag
  163.  
  164. It's also possible to combine the "thisonly" and "corpnet" flags separated by a comma
  165. If the "thisonly" flag is not present then you can try to fetch any base build (19045.1+corpnet, 22621.1+corpnet, 22631.1+corpnet and so on) or a slightly older build
  166. If the "thisonly" flag is active then you should try to fetch the exact internal build number (for example 22631.2424+thisonly,corpnet)
  167.  
  168.  
  169. The MSIT channel can also be useful without the "allow_corpnet" option: it allows you to skip the in-place upgrade in Windows Update and get some of the latest EOL builds
  170.  
  171.  
  172. 7. How to use JSON API
  173.  
  174. If you know what JSON API is and want to use it then this section is for you
  175.  
  176. First, start the server. Then add some builds to your database using any method
  177. After that generate metadata for your added builds using the "Start generating all packs" script option
  178.  
  179. Try to open http://127.0.0.1:44715/json-api/listid.php link in your web browser to make sure everything is working correctly
  180.  
  181.  
  182. 8. How to run the local server in your local network environment (Apache HTTP Server only)
  183.  
  184. If you want to get access to the UUP dump website or JSON API from your another device on your local network then simply edit the "apache\conf\httpd.conf" config file:
  185. Listen 127.0.0.1:44715 --> Listen 44715
  186.  
  187. Change port or your internal IP if you want
  188. Warning: Do not host anything on any public network, this local server is not designed for that
  189.  
  190. You may want to run the Apache HTTP Server as a service using the "scripts\apache-service-aio.cmd" script
  191.  
  192.  
  193. 9. Linux & macOS support
  194.  
  195. Download the "uupdump-x64-v1.5.2.7z" archive and get the UUP Dump website source code from the "uup-dump/website" folder
  196. Host this website on any web server, you can use the PHP built-in server if you don't want to use anything else
  197. For the JSON API to work properly, you should set the environment variable: websiteDir=".."
  198. Dependencies: 7-Zip, PHP 8 + curl, zip, xml extensions
Add Comment
Please, Sign In to add comment