I love you. Seriously.

I would reply you in kind but I think it is against the rules :eek:

Yes I believe it is. But you have no idea how badly I have been wanting this.

Regarding private symbols. There are two leaks, if memory serves me. During Vista, and Windows 8. I can upload them if anyone needs.

Yes it's definitely legit.
However it's not complete (there are different sets of the sources made available to different clients of Microsoft as per their respective agreements and this leak is not a major one...

However, for sharing it here, bro SF42 most certainly deserves a REP and I obviously repped him ! :)

This leak contains sources of the USB, audio, graphics and other drivers along with bits of the UCRT runtimes etc etc...

Could you please upload the Private Symbols :) ? Thanks !

I remember that couple of Windows 10 builds with internal symbols have been leaked a while ago but cannot remember their build numbers.

again, if anyone has those leaks, their upload will be most appreciated

Yes, please upload anything else related to this leak.

Absolutely. Give me a day, max -- my backups are completely disorganized.

I need the build numbers as I honestly cannot start downloading terabytes of Windows 10 builds.

I am more interested in source code and private symbols than whole Windows installations. For Windows symbols I would very much like the latest (or all depending on the total size).

exactly, I also prefer private symbols over whole images

thanks!

The Windows 10 Builds 10.0.15063.0 or 10.0.14393 SOURCES or PRIVATE SYMBOLS would be nice if available please :)

In my experience, the build 10.0.14393 (32-bit version especially) is excellent to be used as the base OS in a VM after "cleaning up" and removing the Windows Store, Defender, Cortana etc from the distro, which interfere with and/or slow our reversing.

So, any PRIVATE symbols and/or SOURCE CODE related to the above-mentioned 2 builds would be good.

The builds later than those are too unstable at the moment for any serious use as a debugging OS IMO.

In the 2 distros named above, I feel that the main SOURCES of use would be for any of the DLLs, EXEs or drivers etc that can be found in the System32 dir in the Windows folder.

Understandably, while we would possibly be not able to compile the files themselves from the sources, the sources and symbols would be invaluable especially for low-level debugging.

Thank you and CHEERS :)

Nobody is interested in x32 OS these days I strongly believe

Its much easier to debug on the 32-bit OS rather than the 64-bit one, especially for hardware like dongles, my friend :)

Once we are done with the debugging and patching/emulating on the 32-bit OS, it becomes a lot faster to port it over to the 64-bit one.

Doing the debugging right from the start on a 64-bit OS, wastes much more time due to enforced driver-signing requirements etc (that need to be bypassed first without breaking the dongle drivers etc in some cases).

That is the reason why not only me but a lot of other researchers also prefer to do their initial debugging on a 32-bit OS if possible.

My "main" OS continues to be a 64-bit one from the last 15 years at least, of course...

Its only for the purposes of debugging, that the 32-bit OS is preferred over the 64-bit one.

Cheers :)

then your way is to 16 (8!?) bit SW :)
it much more coolier taking into account your great posts