Win 10 leak, incl. some source
 

This sounds interesting (if true)...
https://www.theregister.co.uk/2017/06/23/windows_10_leak/

Sounds interesting! Did anyone got their hands on the leaked code?

Don't get too excited as the releasing site has announced:

At a mere 50mb, I am sure everyone would be grabbing and taking a peek.

But all that is known now is that:

that on June 22 And also:

referencing this tweet from Alex Ionescu: claiming that which could still be interesting except for now its not certain who has it besides another cryptic reference to it being on sites such as mega.nz.

On the forum also there is supposedly beyond the most important deleted 50mb "Shared Source Kit", two users "hounsell" and "riley". But the admins are largely going into publicity and cover up mode. Its unclear if this will ever go public or not at this point since the FTP access is quite limited, possibly strictly monitored, and Microsoft by now is trying very hard to micromanage the leak and situation perhaps using rewards or threats, who knows.

Got nothing yet. But the archive seems only about 1~2 GiB. Not possible to have many source code. The full source code should be about 500~1TiB.

Maybe just some hardware driver's code?

Some media in China(https://www.easyaq.com/news/335413423.shtml?from=timeline&isappinstalled=0) have got a sample.

The person that confirmed the leak already stated what bits of source were leaked:

"No source code has been leaked other than the ARM shared source kit."

Could someone please share whatever was already available, by uploading it to some public share service :D ?

I guess I'm just a bit too late ...

if any byte of source was leaked and put on torrent - dont' worry
sooner or later you'll get it for sure :)

Does leak include private symbol servers M$ use internally?

Any Win10 with private symbols ? Ever tried Win7 with private symbols, that helped a LOT !

I did not find the leaked files as well but was not able to cover all the files yet, I did find the following links in which perhaps one of the archives the files will be but I have not downloaded all the files and checked yet.

if it will be interest to anyone here are the links i'm referring to:
https://mega.nz/#F!ZahGCBLY!KbbEnYCwUn0bgZIC0ii43A
https://mega.nz/#F!QXIHQL5b!5dGfiwhD2_sg9YobCh4Mww!dWRzTCCI
http://diskokosmiko.mx/test11/multiup-org-69656/list,1,1

I hope we will find the leaked files soon :)

Matt, where did you find the Win7 symbols?

BetaArchive has the first link info here:
https://www.betaarchive.com/forum/viewtopic.php?t=37253

Here's the shared source kit for Windows 10 build 10.0.14354.1000.

https://mega.nz/#!tuJyTbTQ!jG75YSAp_TTXWeCwTnhYCWgHjqx7OJCo2UyAyTwMi5E

Password: Forumexetoolsdotcom

EDIT: Fixed link

{"success":false,"error":404,"message":"Not Found"}

has anyone extracted the package and can verify it is legit?

Here's the extracted source. It is legit. You cannot start compiling your own Windows with it though :)

https://mega.nz/#!BjYH3YrD!vL3l3Dkzmvu-psJbP18oaD6fsmbS3xgk6js1EjewvQU

Password: Forumexetoolsdotcom

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

You do remember that in the good old days, many of us have had to use Windows 98 (rather than Win XP ) when we needed to use the SOFTICE debugger, as SOFTICE was quite unstable on Windows 2000 and Win XP (until they finally released a patch after more than an year at that time).

Also, for the jump from 16-bit to 32-bit, mostly the issues addressed were related to STABILITY, in teh various releases of Windows, rather than mainly focussing on SECURITY.

Whereas in the transition from 32-bit to 64-bit versions of Windows, mainly for Windows 10 releases, the focus is now more on SECURITY rather than on stability, as the stability (BSODs etc) were not the main issue from XP onwards on properly configuerd systems.

That is why, in my practical experience, driver debugging is a nightmare on the 64-bit versions of Windows 10 due to its numerous security features, compared to its 32-bit counterpart.

Cheers :)

@Fyyre, @sf42

any update on the private symbols?

I have no idea if any of the builds have private symbols or not. Here's a list of what is available.

https://www.betaarchive.com/forum/viewtopic.php?f=2&t=6083&start=475

Can you obtain anything from that list? There are several interesting things which would be great to have there. I would personally like all these things but if the OS are to big then the debug symbols would be very cool as well.

Such as these checked debug symbols:
Added: Microsoft Windows 10 Debug Symbols (10.0.10540.0) (x64chk beta)
Added: Microsoft Windows 10 Debug Symbols (10.0.10540.0) (x86chk beta)

And these checked Windows 10 OS:
Added: 10.0.10540.0.th2_release.150903-1605_amd64chk_client-professional-core_retail_en-us
Added: 10.0.10540.0.th2_release.150903-1605_x86chk_client-professional-core_retail_en-us
Added: 10.0.10575.0.th2_release.151017-2006_amd64chk_client-professional-core_retail_en-us
Added: 10.0.10575.0.th2_release.151017-2006_x86chk_client-professional-core_retail_en-us

Here you go!

Debug symbols: https://mega.nz/#!EGpG3CAC!5UMzYsLat91aG6KmbhL0DET_Kqmdh3u-tYUYlvouxjs

Contains symbols for:

• 10.0.10540.0 x64 (Checked)
• 10.0.10540.0 x86 (Checked)
• 10.0.16251.1000 x86
• 10.0.16278.1000 x64

Debug/Checked Windows Builds:
10.0.10575.0 x64 Pro: https://mega.nz/#!8apCmK5T!I_2LwiCH1uK85PpXSrvGUAlOz5mQ9KA4k-m7W2PTpHs
10.0.10575.0 x86 Pro: https://mega.nz/#!9PpVQA5T!Ap9e5afdRg-G5M_2ySpQqi51-wC6KnmyAw970a8bs48

Password is "eXeTools".

What we are looking for are actually private symbols :)

The "normal" symbols are available freely for download from Microsoft for everyone ... For example, from this page ...

They can also be downloaded as needed from their Symbol Server...

So please share the "private" symbols if possible ...

Thank you :)

The problem is that I have no idea which builds include private symbols!

Can we get the size of the builds, perhaps given the large size of the private symbols, there is a correlation in the build size or some other hint like build numbers or naming convention, etc so we don't have to go through the laborious one by one download task.

Guys, there are lots of tools like pdbdump/etc etc

lets use it over all the *.pdb and compare
profit?

where's the source?