WinReducer 7.0 - FINAL Builds

Yeah I see what you mean. Yes it does not work, even when putting all files back. Maybe it's because the previous programs that slimmed my Windows deleted the entries in the registry or you need more than just these files in order to work. I will try to find it out!

To be sure, I was initially talking about using sysprep to make base images, not lite images or making base images out of lite images   But it would be great if sysprep could work with lite images too, though it might not be easy to find out what is needed for that.

Yes I understood you parapher. My goal is to make it work on my Micro edition because I removed all the stuff with rt-seven-lite, rt-booster, winreducer 1, vLite and manually the lists I have posted here by hand. That's why I came up with over 4000 registry entry errors with CCleaner, Wise Registry Cleaner and Glary Utilities. I could install my Micro edition in VirtualBox run these 3 registry cleaners and capture Windows with sysprep into a new install.wim. I am sure this would make the install.wim even smaller and I wouldn't need to clean up the registry with these programs after a new Windows installation.

I see what you mean, the 4000 reg errors were due to having removed stuff, in part. OK, I somehow didn't get that

You don't need the full WAIK, you can just download the core files via this neat little app: http://theoven.org/index.php?topic=287.0

If you need any scripts to perform certain tasks, let me know I have some.

Ok I just need imagex and that's it

I hope the programs I have used didn't delete the certain sysprep registry entries or I am doomed
Trying to find out which files are needed in order to get sysprep to work...

Hello guys,

I'm working on a solution to clean many unneeded registry values in case you use "Expert - WinSXS Cleanup" ...  

Release date?  

Hey guys,

I've successfully clean the registry with the "EXPERT - WinSXS Cleanup" !!!! So there should be less errors when using it !

Billybully, it will be available tomorrow with the v2.99.4.0 (Pre-Beta Public Build) !  

EDIT : I'm thinking about the fact that using this EXPERT option breaks Windows Error Reporting, so should I need to include it in the "Automatic Removing" preset ?

Do it, lol. Nobody needs Windows Error Reporting. Can't wait for that build  .

And "Boot.wim" registry has been also successfully cleaned !  

Sounds great, winter   Well, I'm off the reinstall my PC, too many things are going wrong and I want to be able to use WinReducer!

 

hey all,

i tried the last hours to recover all my batches from this thread so i will soon look what else is left to reduce.

i also need to say that i like the small WinSxs folder, but i also need to say i got a problem with that.

if and only if i use a unattanded.xml and i used before the winsxs cleanups i get an error at installation, if i use the same iso and delete the unattanded.xml all works fine.

if i remember correctly it had something to do with the windows/winsxs/manifests folder (i also think that i mentioned that some paged ago)

i will try (and hopefully i success) to find whats causing that error.

Did anyone else get this problem?

KrX, for me it works. I am also using an unattended.xml that RT-Seven-Lite created for me. No problems with that...

Also did you use Winreducer to cleanup the WinSXS folder or did you manually removed it like in the list I've posted here?
I know this problem occurs if you have left the pending.xml in the WinSXS folder, maybe you forgot to delete it?

no i just used winreducer to remove stuff, and no no pending.xml left in winsxs

thats the error

i used winreducer to create the unattanded.xml.



and here is my wccf file:

http://www10.zippyshare.com/v/41412706/file.html
it should be an problem at install.wim with the manifest files

Did you check the the language files in the winsxs? For other languages you need of course to change these files. Check the red marked files in the winsxs list. Maybe Winterstorm did it only for US English version but not for others? That's why I purposely marked them red

nop these files and folders are ok, like i said i will investigate it and hopefully i will find the problem

Try to replace all manifests files and see if it works for you? Then you can pinpoint the problem...
Also it is pretty weird because it works for me, for Winterstorm and for Billbully. Maybe it really is a language problem or a bug in the unattended xml file created by Winreducer...

yep after replacing the whole manifest folder everything is ok, now its time to reduce

Try to replace only the associated manifest files from your xml <component name>:

<component name="Microsoft-Windows-International-Core-WinPE
<component name="Microsoft-Windows-Setup"
<component name="Microsoft-Windows-UnattendedJoin"
<component name="Microsoft-Windows-Deployment"

Unfortunately, with v2.99.4.0, I've reproduced the bug experienced by KrX with an "en-US" ISO .... I'm trying to add all manifests files you mentioned to see if that helps ....

Really? It works for me perfect but I didn't make my unattended xml file by Winreducer but by RT-Seven-Lite...

Yep !

Are you able to send me your autounattend file, like this I could see what happen ?

Here it is, works just fine with the slimmed down WinSXS folder:

Thank you so much !

Ok I don't have any <component name="Microsoft-Windows-Deployment" in my XML , try to put manifest files associated with Windows-Deployment in your Manifests folder.

Well guys, new OS install, used a good image I made in February for the install. Got everything installed, finally try out WinReducer, again the same problem. It just hangs early in the process (6 out of 320 in my case). I've tried different configurations but it's just not working at all. This time I also used a different image to reduce, but no go. I'm going to try now to use a non-updated image. If this works, some update is causing it to fail. If it doesn't, I really don't know what the problem is anymore...

@parapher

do you use x86 versions of the tools for winreducer? or x64?

or try to use my winreducer (version 2.99.4.0) with all tools, you just need to configure it.

http://www6.zippyshare.com/v/98363789/file.html

@torrentus

i will try that out