[DISCUSSION] Windows 10 Build 10125

Here are install.wim SHA1 of two ISOs saved as new files from

10125.0.150516-2126.FBL_IMPRESSIVE_CLIENTPRO-CORE_OEMRET_X64FRE_EN-US.ISO

1st
==================================================
Filename : install.wim
MD5 : b166af43c45e3037675d3c4990894850
SHA1 : d0931dd0c0b412ead6b4f18c2e2e1aa9e909683b
CRC32 : 3048b676
SHA-256 : f6ce93a0700b357b8a6f9f8d813d881da133f68017eee75d6ee6495c8fc2ee92
SHA-512 : 040c1c1c4a40ef24d2772760dd7eab3ffae0403ae0abd47b16472b5448e7d112e7384c47cb7ad2bc00d183ebd011c14b84312fc0b321515e6cffc1187a12929a
SHA-384 : 569c49508e3f93a4ef3e6eb7a74baf5721be14e4b617aa7aea09c28437809e7cffaf5c3c85066f56be9eae6ae9b6e2f5
Full Path : E:\Documents\install.wim
Modified Time : 2015/5/17 下午 09:52:10
Created Time : 2015/5/17 下午 09:52:10
File Size : 3,479,839,029
File Version :
Product Version :
Identical :
Extension : wim
File Attributes : A
==================================================

2nd
==================================================
Filename : install.wim
MD5 : b166af43c45e3037675d3c4990894850
SHA1 : d0931dd0c0b412ead6b4f18c2e2e1aa9e909683b
CRC32 : 3048b676
SHA-256 : f6ce93a0700b357b8a6f9f8d813d881da133f68017eee75d6ee6495c8fc2ee92
SHA-512 : 040c1c1c4a40ef24d2772760dd7eab3ffae0403ae0abd47b16472b5448e7d112e7384c47cb7ad2bc00d183ebd011c14b84312fc0b321515e6cffc1187a12929a
SHA-384 : 569c49508e3f93a4ef3e6eb7a74baf5721be14e4b617aa7aea09c28437809e7cffaf5c3c85066f56be9eae6ae9b6e2f5
Full Path : E:\桌面\install.wim
Modified Time : 2015/5/17 下午 09:52:10
Created Time : 2015/5/17 下午 09:52:10
File Size : 3,479,839,029
File Version :
Product Version :
Identical :
Extension : wim
File Attributes : A
==================================================

 

how is possible install.wim match's from one leak ...i trough only Original Released Can match Correct..

 

10125.0.150516-2126.FBL_IMPRESSIVE_CLIENTPRO-CORE_OEMRET_X64FRE_EN-US.ISO


install.wim x64

CRC32:3048B676
MD5: B166AF43C45E3037675D3C4990894850
SHA-1: D0931DD0C0B412EAD6B4F18C2E2E1AA9E909683B
SHA-256: F6CE93A0700B357B8A6F9F8D813D881DA133F68017EEE75D6EE6495C8FC2EE92
SHA-512: 040C1C1C4A40EF24D2772760DD7EAB3FFAE0403AE0ABD47B16472B5448E7D112E7384C47CB7AD2BC00D183EBD011C14B84312FC0B321515E6CFFC1187A12929A

they matchs with my install.wim

and i download the ISOS From the China site...

 

You know Simplified Chinese? (You often mention From the China site.)

 

chinese or japanese i'm not sure it was like this htt p://kuai.xunlei.com/d/MiTzDAJ7JwDAl2JV5de

 

You need to login to view this posts content.

 

It is Chinese.

OK. Glad that you grab a working build.

 

i don't trust issues about chinese or russia or arabic ..i take the risk ..

and i can download from any site using the right click and translate

the most time it

 

There is good or bad people/thing everywhere. Take the one that make you comfortable. You have your say.

 

yeah ...

 

thanks guys

i can repack .wim with replacing corrupted files

but i guess i will redownload

as it will take yours time too

 

Wish you a good time at MDL, and a bright future.

 

Very Good For him!!! Family is the best gift you can have

 

And the house is a gift from one of his clients. Really great! Aint he?

 

You need to login to view this posts content.

 

better use mega.nz its much faster ..and works very good

 

that's why i always use jdownloader

 

i use mega downloader for mega and for other sites IDM..

 

Lexx911 I feel your pain. I have been searching the web for over a week looking for the Synaptics 19.0.6.0 driver. It appears while the Synaptics 19.0.6.0 driver fixes the DPC problem it cause problems in some of Microsoft's new XAML based apps. So in Microsoft's infinite wisdom they decided to roll back Windows Update to a driver that casuses the DPC issse and force you to install it. The DPC issue has been around since W10 build 10061. There are several pages about the DPC issue on the Microsoft forum. Most of them are rants and workarounds. For now I am using the PS/2 Compatible Mouse driver and I am just waiting for Microsoft/Synaptics to fix the problem. The only other thing I can think of is if someone has recently installed the Synaptics 19.0.6.0 driver they could upload it for everyone to use. It would be located here: C:\Windows\SoftwareDistribution\Download\Install\. Note the Synaptics 19.0.6.0 driver would have to be the very last driver installed for it to be here.