WinReducer 7.0 - FINAL Builds

OK torrentus, what I was doing in the mean time was mounting that install.wim and replacing the registry hives from original ISO reg in that lite image again with the updated image reg hives and this time it did install all the way to right before you see the desktop (see image below) and got that same gdiplus.dll error that the person was talking about also.

@Winterstorm and All

I have tested the latest Winreducer v2.99.4.0 with extreme preset and sysprep is also failing to work. 
This happens when you remove Windows components you also need to remove them in the Windows sysprep registry.
In order to fix sysprep you need to do following: 

This happens when you remove System Restore, Windows DRM, Winsat and AuxiliaryDisplay in Winreducer.
Only remove those components you actually removed. No need to remove unnecessary more but I think AuxiliaryDisplay should be always removed in the registry.

Go to HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep
Under following Folders remove:

Cleanup/{ccf004d0-c18e-a2d4-b4ea-08ccb5259f11}     - srcore.dll,SysprepCleanup
Generalize/{ccf004d0-c18e-a2d4-ee22-e585dac90889} - srcore.dll,SysprepGeneralize    

Cleanup/{de7df4f0-0ce9-ca23-6049-1807de6941d3}     - drm2clt.dll,Sysprep

Cleanup/{9733bd0b-72a8-af29-76ba-be8ae2c8be6f}     -  C:\Windows\System32\spwinsat.dll,Sysprep_Clean_WinSAT

Generalize/{b3257dc1-2617-6667-6a6f-2fe2739a2b89}  - C:\Windows\System32\AuxiliaryDisplayClassInstaller.dll,WindowsSideShow_Sysprep_Generalize


--------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Also Windows Search breaks even if you protect it in Winreducer. 

To fix this you need to keep:
System32/NaturalLanguage6.dll
SysWOW64/NaturalLanguage6.dll


Cheers

Ok Parapher try to replace all original gdiplus folders from the Windows/winsxs and also all gdiplus manifest files from Windows/winsxs/manifests. This should work for you. It is strange that for some people it will get an error, never had one...

OK I found all files within the update image's WinSxS folder that had 'gdiplus' in the name and put them into the lite wim. It still gave me the gdiplus.dll error. I then went back and also searched the subfolders in WinSxS and found the Backup and Manifests folder have gdiplus files in it too, so I put all those in the lite wim and tried agian, same error. So I'm not sure where that gdiplus.dll error is coming from. I did a search with the proggie 'Everything' in case I missed a location for gdiplus.dll but I don't think so. I really would like to know if this image would work but can't get past the gdiplus error right now.

This is strange indeed, make a test ISO with a fully replaced WinSXS folder...

Btw, how did you make your lited Windows ISO? Did you use only Winreducer?
First you integrated Windows Updates then syspred and captured it and then started to remove with Winreducer?
I don't know if the winsxs folder cleanup in Winreducer is compatible with integrated Windows Updates...

Yes, I only used WinReducer to make the lite image. And yes, installed in VM, updated fully, sysprep'd and captured.

I saw some additional files with 'gdi' in their names (not gdiplus, but OK) so I'll try to make one more lite iso with the extra gdi files. If that doesn't work, I'll try your suggestion of including the entire WinSxS to see if that helps.

KrX wrote:

hey winterstorm,

i was searching through the batch files billybully, torrentus and i made and what WinReducer did not delete from them.

now i made 2 new batch files with the leftovers for boot.wim

http://www71.zippyshare.com/v/51206579/file.html
http://www71.zippyshare.com/v/77733857/file.html

that saved 61Mb on my boot.wim,
i removed some files that made problems

maybe some ppl could try them if they also work for them and after that you could add that to Winreducer maybe.

as soon as i have done that also with the install.wim batches i will post that too.

Hey KrX,

Got your files, thank you !

KrX wrote:

@winterstorm

one question why does winreducer (if selected winsxs cleanup AND Winsxs compression) dies first the compression and after that the cleanup?

wouldnt it be faster if it cleans first the winsxs folder and after that compress it? because it needs to compress less files after the cleanup.

Yes, that's an excellent idea, it will be changed in v2.99.4.1, it should be available Sunday.

parapher wrote:

Winter,

The problems I'm having with WinReducer definitely have to do with using my updated install.wim's. I just tried a original SP1 iso and WR runs right through it, no problem.

When people use sysprep (many IT persons use sysprep to deploy images, etc.) you basically install the Windows edition it is made as; in other words, if you use an Ultimate image, when you install it in the VM and sysprep it, the install.wim that is a result of that process will be Ultimate. Meaning, when I use WinReducer on an updated install.wim made with sysprep, only the Ultimate image will be listed for mounting. So instead of seeing all the Windows editions inside, like HomeBasic, etc., I only see Ultimate when I mount the image in WinReducer.

Maybe this is one of the things causing this problem. As you said, you used an updated image in February. But I'm assuming it was made using offline integration, which would leave the image count inside intact. Perhaps that's the problem. However, it should work with images that have only 1 image inside.

It is also possible that my images have more updated files inside because I use the LDR method of installation of updates, so perhaps some driver-related update (like the USB updates caused problems for vLite) is causing problems.

Yes, you are right, when I told you that I used a February Updated ISO, I should mention that I always use offline integration.

On your sysprep ISO, could you please send me the file for this command :

...\ImageX.exe /info "...\sources\install.wim" > "%USERPROFILE%\Edition.txt"

(replace "..." by the correct path). Thank you.

Yes, it could also be a windows update that troubles WinReducer.

@Torrentus : I will integrate your fix for sysprep, tomorrow, because I need to go to sleep ... Thank you so much in the meantime !

AHA! Some new findings.

OK, I scanned any file with the word "gdi" in it (not just "gdiplus") and gathered those files. I placed them in the lite install.wim and then my lite Win7 install worked!

This is the list of gdi files (all of them) that I gathered and placed in the install.wim:


(the above also shows the Backup and Manifests folders in the paths)

So I can make lite images, but the registry hives (or perhaps only the System one torrentus suggest, I still have to test that) were causing the fail. So I replaced the hives with the original ISO ones to make WR work, then after making the lite image, replaced the registry hives again but with the updated ISO hives. Then I don't get the BSOD but I get the gdiplus.dll error. So then I placed the above-mentioned gdi files in the WinSxS and then it worked, I'm on the desktop in the VM now

That's why I said you guys should leave feedback on the new winsxs cleanup  . I didn't integrate Windows Updates before slimming my Windows, I always integrate them after I slimmed my Windows offline. Like I said, I like it that way better, make your final slimmed down Windows as base image and then when you want to integrate new Windows Updates after a long time again use my WinSXS Repair Tutorial . Integrate all Windows Updates and then cleanup again the winsxs folder. 

With this method you don't need to start from the beginning or encounter any errors. This works perfectly. 

Anyway, Parapher if you want you could find out which of these files ( the absolute minimum ) are needed to make those people happy that are integrating their Windows Updates before slimming  . I can give you some tips how I did it with over 7000 manifest files, those you listed are a piece of cake.

First I would exclude all Backup files/folders , then if it works you remove all wow64 files/folders. If you get somewhere the error you go back and remove only 50%. Then try again. If it works remove once again 50% and so on till you get only 1 folder. You do the same with amd64 folders. You would not need to do this with the x86 folders because after you pinpoint all amd64 folders you need the same version. Finally do the same with individual manifest files. The most efficient way I encountered is to reduce possibilities always by half, something like that .

So Torrentus, do you think once those sysprep changes are implemented in WinReducer, I could actually sysprep my lite VM install?

Yes I already syspreped my Micro edition, once Winterstorm fixes it it will work for you too or you can do it yourself now.

Just follow this Guide for those who only used Winreducer 7 v.3 

or 

this Guide for those who used RT7-Lite, RT-Booster, old Winreducer v.1, vLite or manual system files removal  

Cool.

The gdi files in the WinSxS\Backup folder that I mentioned don't have to be included to prevent that gdiplus error. I just tried it with another install and no errors.

I haven't narrowed it down further so I still got all the gdi files in WinSxS main folder and Manifests folder.

Hello guys,

Amazing work on this ! And yes, I will integrate in the next build (2.99.4.1) which will be released tomorrow !

@Torrentus and Parapher : Guys, if you have time tomorrow, I will send you a link with a test build (before public release), like this you could confirm if it will work or not ...  

EDIT : It has been faster than I think but I should have found a fix for the "gdiplus.dll" bug. Could you please test the build in the link I send you by PM. Thank you very much !

Thanks, winter, I'll test it today

EDIT: I replaced the SYSTEM registry hive in my updated (sysprep'd) Win7 x64 image with the SYSTEM hive from the original MS image. However, WinReducer still got stuck at the point where it was removing Freecell (game) like it did yesterday. So, Torrentus, I don't think it's a matter of only replacing the SYSTEM hive, I think the SOFTWARE hive also needs to be replaced. I'll run another test and I was thinking of replacing SOFTWARE only, to test if it is the SYSTEM hive, SOFTWARE hive, or both that are needed.

EDIT2: This time I did not replace the SYSTEM registry hive (I kept the one from updated sysprep image) but I did replace the SOFTWARE hive. And now WR successfully finished the session, so I think it is the SOFTWARE hive causing the problems for WR when it is run with sysprep'd images. It was also having the hanging problem on base images (not updated) that were sysprep'd, so I know the problem was not due to Windows updates, but it is due to whatever sysprep does to the SOFTWARE hive of the registry. I still have to test the install in VM though   I'll report back and see if the gdiplus problem was solved with this new WR test build.

EDIT3: Success! The WinReducer test build has the gdiplus.dll error fixed. Good job, winter! So now it appears the only major problem is when using WinReducer on sysprep'd images, that the SOFTWARE registry hive (System32\config) gets altered by the vm/sysprep process in such a way that WR is unable to work with it. That's still a mystery. But replacing the SOFTWARE hive of sysprep'd images with those of original MS images does not seem to hurt the resulting installs. I even ran Windows Update and it offered no new updates so it was reading all installed/integrated updates as present; in other words, the registry replacement did not mess that up.

OK,

Just a question, did you also remove :

- "Features - Windows Media Player"
- and/or "Accessories - Windows Recovery Environment"
- and/or "Network - Internet Explorer (Engine)"
- and/or "Services - Superfetch Service"
- and/or "Services - Telephony Services"
- and/or "Services - Windows Error Reporting Service"
- and/or "Services - Windows Update Service"

I will have probably other questions ...  

EDIT : I've updated all these WinReducer Components to remove Sysprep registry key based on the excellent Torrentus Guide ! A new testing build is available (--> build time = 8:31pm).

I'm not sure what all changed with the latest test build but it breaks many things now. I didn't even remove any Feature (only DVD Maker which I did before without problem) but now there are some major problems:

EDIT! Sorry, no problem, it was the registry hives again. Apparently, when using the sysprep'd images you have to replace all the registry hives in the config folder again with the ones from the updated image or IE11, WMP, etc., don't work.

So to be clear, to get sysprep'd images to work with WinReducer, you have to:
a) replace updated sysprep'd image registry hives with the ones from the MS Sp1 original iso
b) run WinReducer on that image
c) once WinReducer is done, replace the reg hives again with the updated/sysprep'd ones.

Now I will try to run sysrep on the lite install in vm, to see if that works.

OK, thank you very much for your feedback !

@Parapher and Torrentus : New testing build available (build time = 11:29 PM) (Fix for Windows Explorer Search Bar bug), it should be the last one before the public release ...  

Good work Winterstorm  . Also I am not so sure how you could debug and pinpoint Parapher's registry error. Maybe it's impossible because sysprep is keeping installed registry information in the System and Software registry hives which are making problems for Winreducer. The only solution that is also logical, is Parapher's temporarily registry switch

Hey Torrentus, I just installed and cleaned the WR image in a VM and tried sysprep, but sysprep got a fatal error. So this is not working for me with the latest WR. Just something to look into, maybe you and winter can figure out how to get it to work

Also, if you disable a lot of the CPL items, many of them remain as blank icons. Also, some of the removed ones remain intact, like Parental, and still start up. I'm keeping a list of stuff that I'll post later. But for now, sysprep is not working (and that's with the updated reg hives in place so it's not a reg issue I think).


EDIT: Torrentus, in your sysprep fix post, did you by any chance mean:

Cleanup/{de7df4f0-0ce9-ca23-6049-1807de6941d3}     - dmv2clt.dll,Sysprep ?

In the post you mention:

Cleanup/{de7df4f0-0ce9-ca23-6049-1807de6941d3}     - drm2clt.dll,Sysprep

It's weird, on my host OS I can see the drm2clit you mention, but in the vm I see the dmv2clt instead. Weird?


EDIT2: I just tried the sysprep fix but I still got a fatal error (although I did remove the above dmv key, there was no drm dll). By the way, Torrentus, what component in WinReducer related to DRM, WinSAT and the other things you mention? I thought of doing a build without those parts removed, to see if sysprep works then. But I can't figure out what component DRM, WinSAT, etc., relate to.

I don't know if Winterstorm already fixed it, maybe in the new upcoming build? 

Anyways for me its drm2clt.dll.

Taken from the first guide:

Go to HKLM\Software\Microsoft\Windows\CurrentVersion\Setup\Sysprep 
First you need to clean the Cleanup folder. In the Data value there are various paths to Windows dll's.

You need to check which dll's are missing from your slimmed down Windows. Best way to do this is go to your Windows folder and search for all dll's which are listed in the Cleanup folder in the registry. If some are missing from your Windows you need to delete the entries. 
  
Then you go to the Generalize and Specialize folder in the registry and also check the dll's in the data value. If some are missing delete them. 

Also I think you always need to delete Generalize/{b3257dc1-2617-6667-6a6f-2fe2739a2b89}  - C:\Windows\System32\AuxiliaryDisplayClassInstaller.dll,WindowsSideShow_Sysprep_Generalize
Despite it's in your Windows folder or not...


Also check for errors in the log file of your sysprep. It's in Windows/System32/sysprep/Panther/setupact.log

If the fatal error occors it's in the log file mostly at the bottom under ERROR. There you see which dll is the culprit that you need to delete from the registry...

Thanks for the tips. When I check the sysprep log, it is saying the following:

setuperr.log:

sysprp launchDll: could not load DLL srcore.dll [gle=0x0000007e]
an error occurred while running registry sysprep DLLs, halting sysprep exectuion.

setupact.log:

(everything returns successful until:)

will try to launch 'srcore.dll,SysprepCleanup'
ERROR: sysprp launchdll: could not load DLL srcore.dll


Looks like srcore.dll is a WinSxS file?

Alright, I was able to successfully complete sysprep on the lite install! In my case it was srcore.dll reg entry at first, then when I fixed that it became ipsmigrationplugin.dll so I removed that reg entry too. I also removed the auxiliary display entry like Torrentus suggested. Then it worked! I'm going to capture the image now and try to install it.

EDIT: Success! Install went fine. What I did before sysprep was use gpedit.msc to remove the blank CPL items so everything looked neat for the capture. I also did some heavy reg cleaning with several apps. Cool, finally getting somewhere for me

Hello,

parapher wrote:

Also, if you disable a lot of the CPL items, many of them remain as blank icons. Also, some of the removed ones remain intact, like Parental, and still start up. I'm keeping a list of stuff that I'll post later. But for now, sysprep is not working (and that's with the updated reg hives in place so it's not a reg issue I think).

Are you sure to also check (to remove) all according Control Panels ? But you could also use the "Presets - Automatic Removing", did you  ?

parapher wrote:

It's weird, on my host OS I can see the drm2clit you mention, but in the vm I see the dmv2clt instead. Weird?

Yes, more than weird ! But I will update to remove both, if necessary.

I need to delay a little bit the public release because unfortunately I'm facing an installation bug with the latest build I made so I need to figure it out to fix that. I've also update all sysprep registry and improve some components cleanup ...

I will release a new internal testing build today !

Finally fix the installation bug, I will release the test build soon !  

It's available !

@Parapher or Torrentus : could you please confirm that all sysprep keys are removed in the registry ! Thank you very much for your help.

EDIT : Build Time : 2:45 PM

THanks, winter!

About the dmv2clt sysprep registry entry, to get my latest image to work I didn't need to remove it. It just depends on which components you remove. I did not yet do a full/extreme removal, so maybe then it would be necessary to remove the dmv entry, but you would have to check that in more detail. I'm sure you know that, but just trying to clarify what I meant when I couldn't find the drm entry that Torrentus was talking about earlier

By the way, it's really great that we can use sysprep on the lite images now, especially in relation to the registry. It seemed to be OK to replace the registry hives with the ones from the updated images after using WinReducer on an image, but now with sysprep we can install to VM, do reg cleaning, and capture the actual install with registries that match the image.  

EDIT: Winter, I did select the automatic removing process under presets, so those CPL items still did not get removed. I'll let you know if I found out more about this.

Ok will test v2.99.4.1 now , I am pretty busy at the moment. Lots of other stuff to do