Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


nuhi

vLite 1.1 beta - vBloat

Recommended Posts

Is it safe to remove contents of this folder?

C:\Windows\SoftwareDistribution\Download

yes it is

Share this post


Link to post
Share on other sites

Hi all,

Tested vlite 1.1. Integrated not only all applicable to my notebook hotfixes and drivers, but even this vista ult poker game and dreamscene. So vlite integrates even cab files!!!

Everything worked without a flaw!

Just amazing! Nothing else to report!

Thank You, Nuhi!

Pls do not forget to fix lsm error in future versions!

Alex

Share this post


Link to post
Share on other sites

It doesn't seem to be working, when I hit apply all I get is a Unhandled exception error:

See the end of this message for details on invoking 
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at ..()
at ..(Object , EventArgs )
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

Edited by nuhi
cut

Share this post


Link to post
Share on other sites

KnightCrawler1, is that before or after the Apply window popup, do you click OK then that happens or even before, on the very Apply button click?

Does the processing starts?

Share this post


Link to post
Share on other sites
KnightCrawler1, is that before or after the Apply window popup, do you click OK then that happens or even before, on the very Apply button click?

Does the processing starts?

Nevermind I fixed the problem, I was using another custom disc and this time used the original OEM DVD as the source.

Share this post


Link to post
Share on other sites

I cannot remove the default features (Remote Differential, Ultimate Extras, some others) from a vLited Vista SP1 under Programs And Features, just get a standard error.

All components removed except App Compatibility and Class Scheduler.

Share this post


Link to post
Share on other sites

KnightCrawler1, aa right, AIO, I forgot about that.

UKSimon, fixed in next version, can't be manually fixed so please have patience.

Share this post


Link to post
Share on other sites

That's good to know Nuhi thanks, can I ask what was causing it to fail? It would do the same when I disabled some service from a default Vista install.

Share this post


Link to post
Share on other sites
no bug. You got the GDR version of the fix (16xxx). You can only get the QFE Version (20xxx) if you have already integrated a QFE Update for the file.

Can you explain more please? I've found more SHELL32.DLL files on my system:

C:\WINDOWS\SYSTEM32\SHELL32.DLL -> 6.0.6000.16513

C:\Windows\winsxs\x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.16386_none_69f268e21510dceb\SHELL32.DLL -> 6.0.6000.16386

C:\Windows\winsxs\x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.16513_none_6a3b1b4414dac79d\SHELL32.DLL -> 6.0.6000.16513

C:\Windows\winsxs\x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.20628_none_6abee9952dfc020b\SHELL32.DLL -> 6.0.6000.20628

Which one is system using?????????

NUHI, can you do something with this??? I am thinking, that Windows is using the one in %WINDIR%\SYSTEM32 folder, so not using the newest version.

Have tried integration with WUI 0.9.2.5 (Vista Update Integrator)...and it is the same. Starting VirtualPC and I am going to install clean original Vista, and then I will install the updates manually....I will post the report. :)

Edited by mhyll

Share this post


Link to post
Share on other sites

mhyll, that's how MS does it, they keep old versions in the winsxs cache after you install/integrate a hotfix. It's beyond any logic except for the uninstalls, but who would want that after the OS install. Anyway I will be exploring an option to clean out the old files, they are annoying me as well.

It is probably using only the newest, check the properties of the one in the system32.

Share this post


Link to post
Share on other sites
mhyll, that's how MS does it, they keep old versions in the winsxs cache after you install/integrate a hotfix. It's beyond any logic except for the uninstalls, but who would want that after the OS install. Anyway I will be exploring an option to clean out the old files, they are annoying me as well.

It is probably using only the newest, check the properties of the one in the system32.

Ok...I installed the original Windows Vista and run through Windows Update. It's still the same. I don't know, what's happening.

C:\WINDOWS\SYSTEM32\SHELL32.DLL -> ver. 6.0.6000.16513

C:\Windows\winsxs\x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.16386_none_69f268e21510dceb\SHELL32.DLL -> ver. 6.0.6000.16386

C:\Windows\winsxs\x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.16513_none_6a3b1b4414dac79d\SHELL32.DLL -> ver. 6.0.6000.16513

C:\Windows\winsxs\x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.20628_none_6abee9952dfc020b\SHELL32.DLL -> ver. 6.0.6000.20628

Any idea now???? It is situation AFTER REGULAR WINDOWS UPDATE!!! Is Windows using the newest one in WinSXS directory or what???

Edited by mhyll

Share this post


Link to post
Share on other sites
mhyll, that's how MS does it, they keep old versions in the winsxs cache after you install/integrate a hotfix. It's beyond any logic except for the uninstalls, but who would want that after the OS install. Anyway I will be exploring an option to clean out the old files, they are annoying me as well.

It is probably using only the newest, check the properties of the one in the system32.

Ok...I installed the original Windows Vista and run through Windows Update. It's still the same. I don't know, what's happening.

C:\WINDOWS\SYSTEM32\SHELL32.DLL -> ver. 6.0.6000.16513

C:\Windows\winsxs\x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.16386_none_69f268e21510dceb\SHELL32.DLL -> ver. 6.0.6000.16386

C:\Windows\winsxs\x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.16513_none_6a3b1b4414dac79d\SHELL32.DLL -> ver. 6.0.6000.16513

C:\Windows\winsxs\x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.20628_none_6abee9952dfc020b\SHELL32.DLL -> ver. 6.0.6000.20628

Any idea now???? It is situation AFTER REGULAR WINDOWS UPDATE!!! Is Windows using the newest one in WinSXS directory or what???

OK. EVERYTHING IS OOOOOK!!!! :)

Looked into the _MANIFEST_.CIX.XML file in WINDOWS6.0-KB938979-X86.CAB. It contains BOTH versions, 16513 and 20628!!! Both SHELL32.DLL files are axactly tha same size!!! So probably, this are the same, but for different Vista editions.

Here is the proof from that XML file.

- <File id="108" name="x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.20628_none_6abee9952dfc020b\shell32.dll" length="11315200" time="128273842777710000" attr="32">
<Hash alg="SHA1" value="a6dd82a2bb7b02b7efb6f6205e303cb87c9e38f0" />
- <Delta>
- <Source type="PA30" name="42">
<Hash alg="SHA1" value="cab075ad886b13bf7db2da4b9c571cb06b70f83f" />
</Source>
<Basis file="4" />
</Delta>
</File>
- <File id="107" name="x86_microsoft-windows-shell32_31bf3856ad364e35_6.0.6000.16513_none_6a3b1b4414dac79d\shell32.dll" length="11315200" time="128273846077560000" attr="32">
<Hash alg="SHA1" value="22933024bd51ac73495a9884c93b35e4560ed7ec" />
- <Delta>
- <Source type="PA30" name="43">
<Hash alg="SHA1" value="4dd27a5e3b3d97cef91866f2e0c65c856145da39" />
</Source>
<Basis file="108" />
</Delta>
</File>

The same is also with other files packed in this hotfix. So hotfixes are fine, 16513 is the RIGHT version of the file. :)

I am happy.....great work NUHI....but if it possible to somehow clean out those old versions, it would be great. :)

Edited by mhyll

Share this post


Link to post
Share on other sites
It contains BOTH versions, 16513 and 20628!!! Both SHELL32.DLL files are axactly tha same size!!! So probably, this are the same, but for different Vista editions.

no, read my post and you will know, which file is being installed when you run the update.

Share this post


Link to post
Share on other sites
It contains BOTH versions, 16513 and 20628!!! Both SHELL32.DLL files are axactly tha same size!!! So probably, this are the same, but for different Vista editions.

no, read my post and you will know, which file is being installed when you run the update.

PLS, can you explain GDR and QFE????

Edited by mhyll

Share this post


Link to post
Share on other sites

QDR Updates are Offices Updates from MS to fix a general problem (security issue, major issues). QFE (Quick Fix Engineering) Updates are made for a specific problem and are only available per request. These fixes are not tested against all combinations of installed Updates and can cause problems. You should only install such a fix, if you have the problem mentioned in the KB article.

If you have applied such a fix, the version number is 20xxx to indicate that the file is from a QFE Fix. If you install a QDR Update that updater takes a look at you current installed file and checks if the file is version 16xxx (offical update or RTM version). If this is true the installer installs the 16xxx version of the update otherwise if the fileversion of your installed file is 20xxx (file from a QFE Update) the installer takes the 20xxx version.

Because you have used the RTM version of Vista, the installer found the shell32.dll in version 16386, so the installer installed the shell32.dll in version 16513.

But I have no idea, why the installer places the Shell32.dll Version 20628 inside the WinSxS folder.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...