EX-100 - v3.1.0.0 [ALL]

What's New!!!!

When you release new build?

Hello guys,

I confirm the new build release for today, with the "EX-100 Updates Catalog" ...

There will be 2 new important options (to improve "EXPERT - Net Framework Complete Cleanup") :
- "WinReducer Software Compatibility" : this will keep all necessary net framework files to use with the WinReducer Software (exactly the same as in the previous EX-100 build). If you disable it, it will remove around 50 Mo but you will lose the WinReducer Compatibility 
- "Extended Software Compatibility" : This will be a generic software compatibility (like Intel HD Graphics CPL, or MS Office)

So, if you enable these 2 options, you will have a better compatibility for many net framework based software while you using Net Framework complete cleanup.

But if you disable these 2 options, you will completely remove the Net Framework installed. This is a difference from all previous EX-100 builds because with the new build, you will have the possibility to manually choose to entirely remove Net Framework.

And as always, once you remove Net Framework, you will not be able to restore it or install a new version.

I wish you to have a nice day !

cant get windows 14316 to work no more......with...6.50   or 6.60

Hey drew24,

As soon as I'm able to get a recent RS1 build I will test this

But for the moment, EX-100 is officially supporting TH1 and TH2

tanks m8... just now did 1 with pro 1511  went well

Hi,
I am on the impression that the recovery compression is not take in account for the OOEB files.
Can somebody confirm?
Thanks

when create install. wim, it's corrupted. and then, dumb built the ISO file.
 hi everyone

Hello,

For the moment my main problem is to download this Windows 10 Build. I guess I have to wait the new ISO which will be available this week, as far as I know.

I remember you that these RS1 builds are not stable enough to consider them as final build, which explains why Microsoft will release it only on July

I will release the final EX-100 build in June (for TH1 and TH2), then I will start the complete RS1 support

Hello,

I finally got a 14316 build, thanks to Hen Ry

So bad news, and what is weird, this is a Dism error, even the one used by WinReducer (latest official version for TH2 10586)... which is not able to process all necessary tasks to correctly detect this build, even the mount process is not working !

I've improved the WinReducer detection to avoid the actual bug (software crash), and this update will be released Sunday.

For the moment, the build 14316 is not supported and I'm working to find a working solution.

Hello guys !
I bought a Microsoft Windows 10 Home, 32/64 bit, English, Retail, USB.
I tried Winreducer EX-100 - v0.6.6.0 and ...

  

Hello,

Are you trying to open Windows 10 directly from the USB key ?

Yes, I tried ...
Windows works. I wanted to open it and update it with Winreducer

Try to copy all the usb key content in a folder in your HDD or SSD, then try to open this folder as usual, and let me know the result 

I copied in a folder, as I usually do when I work with winreducer

I do not think that I will use Windows. Always I download the latest. I was just curious. 

I breathe easier ... 

I made a ISO and, voilà! 
So I chose only 64 bit and is OK now...


P S - How can delete write protected files.

ruby2hora wrote:

I breathe easier ... 

I made a ISO and, voilà! 
So I chose only 64 bit and is OK now...

Ok, good news

ruby2hora wrote:

P S - How can delete write protected files.

This is for your protection, in order to avoid deleting the files you purchased. But if you want to do it anyway, just right clic on the folders and remove the read-only flag, it should be the trick.

winterstorm2050 wrote:

Hello,

I finally got a 14316 build, thanks to Hen Ry

So bad news, and what is weird, this is a Dism error, even the one used by WinReducer (latest official version for TH2 10586)... which is not able to process all necessary tasks to correctly detect this build, even the mount process is not working !

I've improved the WinReducer detection to avoid the actual bug (software crash), and this update will be released Sunday.

For the moment, the build 14316 is not supported and I'm working to find a working solution.

I've also downloaded a fresh 14328, and it seems to be solved in this new build, so you should be able to use 14328, for testing purpose only, at least for the moment

hey guys it looks like 6.60   worked with my insiders preview 14332.....tested on vmware   all went great....u guys give it a try
...btw i am using my wccf i had from 5.40

With me came in the last two getting the error.

[You must be registered and logged in to see this link.]

Hen Ry ..i had that to   so  give it a try m8 -with IP-14332

c here[img][/img]

drew24 wrote:

Hen Ry ..i had that to   so  give it a try m8 -with IP-14332

so the error does not happen with the newest version of win10?

so i will drop my tests

sorry guys 2nd try with 6.60,,,with IP-14332 got this again [img][/img][img][/img][img][/img]     wow i wonder why the frist one i did went great i used the same wccf then this happen  wat a bummer

ok so i will test again to get the component that cause this

morning all KrX    believe it or not ... i did a customize of the  IP -14332 i made with winreducer 6.60 earlier and did get 6.60 to work again   ...not the orginal IP -14332 which i got from Insiders... cant seem to find where the bug is....[img][/img]  so keep testing m8.....will do a nother later this weekend

it´s really funny thats it´s working sometimes and sometimes not for you xD

the component is probably somewhere at Network (but i got languages and keyboards also left for testing)

most suspicious is one of the remote components for me