Draft:List of builds with components stored on the Microsoft Symbol Server

This is a list of builds with components stored on the Microsoft Symbol Server.

Large (thousands) of components recoverable
Any build before the introduction of reproducible builds around 1498x is included in this list.

Windows 8
- Recovered 250 files so far, ~3-5000 to go

Kernel recoverable, as well as components that do not change between builds
The kernel was not subject to reproducible builds until early 19h1 and therefore has a valid TimeDateStamp that can be used to bruteforce symsrv urls. RS2 was the first to have daily builds pushed, as evidenced by 14993 having valid symsrv links. 14357 does not, but the rs1 branch has not been checked, only rs1_release. Before then only RTMs and major milestones (5112 (deleted 2020), 5384, 5600, 5744, 6000, 6001, 6002, 6519, 6608, 6801, 7000, 7100, 7600, 7601, 7850, 7950, 8102, 8250, 8400, 9200, 9347?, 9431, 9600, 10240, 10586, 14393, etc)

Only files that do not change between builds recoverable (small minority of components)
Any build after some RS5 - certainly after 17763 is of this nature. They usually get pushed 1-2 days post compile.

Builds get pushed usually but not always daily, usually from current branches (ni_release, rs_prerelease, etc) - files that don't have datetimestamp and imagesize change

Buildtag not obtainable due to "WinBuild.160101.0800" caused by reproducible builds - only some setup files still have builds

Vibranium
(vb_release probably => .1)

Nickel
- nothing pushed since 5/9. probably rtm.

Copper
Other components are stored but as the TimeDateStamp is unpredictable obtaining them is computationally infeasible.

Pending checks
- Official Milestone 1 build of Windows 8.1, should have been pushed. RS1 branch WinMain fbl_release (TH1) - 9824, 9826, 9828 DP2. DP3, DP5, DP6, DP8 (DP1 was the public DP, DP4 CP, DP7 was Windows 8 build 8375)

Once on the symbol server, but removed
- Removed in 2020?

Likely confirmed to NOT exist
- pivotman checked for this. May double-check, image size changes are possible...?

fbl_partner_outXX