[monkie53]

Well after using Vlite with the win 7 dll's I think I have found a much simplier way to get the files to werk with the original Vlite..

Here is the short story..

After running Vlite on these new SP1 MSDN iso files we get corrupted files, with using the win 7 dll's its possible to run Vlite and it will work, then again more issues than good with this, ( trial and error here )..

SO I looked at a RTLited iso I had after Vlite had failed I thought well wont hurt to run it through Vlite,.. yea JUST to see what happens...

Well to my amazement, it didnt get corrupted!!

Ok, so I was like this is good, I then started looking into what why who, all those things.

The only thing I could find that had any kind of offset was date/time of the folders/files inside the install.wim .....

Here I thought, ok what if I took my untouched iso files and mounted the version I needed ( Ultimate ) and changed the date/time on the windows and winsxs folders.. So I did.

It was a kinda long process to wait for the takeown to run on 5.52GB of winsxs folders/files but it was worth it, I then changed the date/time back to, yep ya guessed it, July 13 2009 for the WIndows and winsxs folder.

unmounted commiting changes, ran it thru Vlite and test install went flawlessly using the default Vlite files for Vista..

So what does this mean, I have no darn clue, but changing the date/time on the windows and winsxs folder was all I needed, I tested this on the other version in my x64 to see if it was just a fluke and I spent all last night testing and it werks for all versions for x64

x86 not so sure about, but surly there is some sort of werk around if x86 is effected too.

Simply put - mount the version you need and takeown of the entire winsxs folder and after that has ran and you know own that folder just use a app to change the date/time of the windows and winsxs folder to the July 13 2009 for Last Accessed, Date Created, and Date Modified the time can be whatever ya prefer.

Also you may want to make a copy of the folder of the source files after the unmount/commit so this way you have a fresh files to work with after testing it in Vlite ( new fresh clean files unmodded )

So if you have used my silly and crazy method above just un do it by making sure you uninstall the modded wimfltr.inf with the InstWimFltr.exe from JFK removing the Vlite you are currently using ( to get rid of all those files etc.. ) making sure to reboot after the uninstall of these modded files. then install the 1.2 version of Vlite.

then do the simple - mount - takeown - change date/time on windows folder and winsxs ( time here about 15 minutes ~ ) - unmount/commit - run the results thru Vlite ( original ) - test in virtual box etc..

Hope this werks better than the crazy modded Vlite files like it has for me ( no issues at all with Vlite Now YaY )

If anyone tries it, lets hear about it

This post has been edited by monkie53: 24 February 2011 - 01:53 AM

[romantiq]

I wish I tell that your - everyone - solution solved my problem, but my "lite" installation of W7 SP1 vlited fails - after first restart of installation - with a blank screen, with white text, telling me that : "Windows fails to start" with error code 0xc0000428, "Windows cannot verify digital signature of file : C:\Windows\System32\winload.exe", and inviting me to reboot with Windows 7 repair disc. In fact, i tried many times to install.
BUT, if SP1 is slipstreamed in original kit - with original 07/13/09 files (i found that kind of kit in a Legolash release) - w7 vlited installation works without any problem !!! In fact i applied that solution in my computer and works even today. Seems like 11/20/2010 kit have a compatibility problem (in vlite I see 3 patches in that kit, and vlite label that kit "Windows 7 with Service Pack 1", ... in 07/13/2009 I can see just SP1 patch and no reffrerence to SP1 in the very first screen after launching application.

[bapt]

how to change the date and time of the Windows and Winsxs folder?
when using vLite, we did not have time to make this change?

if you mount the image before using Vlite date is July 13, 2009 and 8:20 p.m.

how can we do?

thanks

EDIT: I compared the dates/times (creation of file and date modified)
after using Vlite modded and true Vlite and that the same (et also Rt7lite)

I don't know what to do

This post has been edited by bapt: 24 February 2011 - 05:46 AM

[woowo]

i think vlite is still really good.

[romantiq]

Bapt, your image is based to original 07/13/2009 kit (I vlited this kit with no problems - see my post ...) so you dont need to modify the date. Date modification maybe useful for the "11/20/2010 SP1 kit". Btw, I used Total Commander for that task (submenu Change Attributes in Files menu).

[romantiq]

named "07/13/2009 kit", the one that have SP1 slipstreamed. Vlite works perfect with that image.

[bapt]

Indeed, if I integrate SP1 to Windows 7 ISO, Vlite works fine
if I use Windows 7 SP1, there are problems with Vlite

what is the difference between a Windows 7 SP1 and Windows 7 with sp1 integrated

just the SP1 Update in Windows 7 sp1?

and I still do not understand the history to change the date and time ^ ^

romantiq, on 24 February 2011 - 06:58 AM, said:

named "07/13/2009 kit", the one that have SP1 slipstreamed. Vlite works perfect with that image.

what do I have to rename in 07/13/2009 Kit (with windows 7 sp1 MSDN?)

I watched with a Windows 7 and sp1 integrated
date of install.wim (example) is the January 17, 2011 and no problems with Vlite

I do not know what to Modify

thanks

EDIT:

for the windows folder

creation date: 13 July 2009
modifiaction date: February 23, 2011

same for the winsxs folder

This post has been edited by bapt: 24 February 2011 - 08:35 AM

[romantiq]

Dates of install.wim or boot wim are not relevant, is the date of release creation (depends of the creator) , but the rest of files date is 11/20/2010 when SP1 MSDN was released. Setup files, bootmgr and many other files are different (not just by date) between images and I think that vlite have problems with newest SP1 files.

[bapt]

romantiq, on 24 February 2011 - 08:45 AM, said:

Dates of install.wim or boot wim are not relevant, is the date of release creation (depends of the creator) , but the rest of files date is 11/20/2010 when SP1 MSDN was released. Setup files, bootmgr and many other files are different (not just by date) between images and I think that vlite have problems with newest SP1 files.

and what needs to be changed then?
for Windows sp1 MSDN works with Vlite

that's what I do not understand

thank you very much

[romantiq]

Sorry for my english too (I am romanian) ... My work with Windows 7 is a little bit complex, because I use "7elite32" method for size reduction (vlite + some batches, another topic in this forum). This metod worked fine with original W7 kit, but in W7SP1 case my problem is the poor size reduction applied to original W7 kit+SP1. So I have tried MSDN SP1 kit and - surprize - vlited image don't work ! Windows cannot start after the first reboot . Too shame because the image and installation size both are very small, much smaller than image obtained with W7 original+SP1. I am sure that vlite must be "adapted" to the MSDN kit and therefore I believe that replacing wimfltr and wimgapi is seemed a good ideea.

[bapt]

ok, so Vlite works great with Windows 7 and sp1 integrated but not with windows 7 sp1 MDSN

with the method of monkie53 (replaced wimfltr and wimgapi) the problem is that Vlite closes itself after the removal of components (we just unmount the image with dism but some "adjustments"are not applied)

for example, I disable UAC, but the padlocks are still some folder
and I delete "file and printer sharing (Server) but I still have these options in Windows 7 after installation

how to have Vlite compatible with Windows 7 sp1 MSDN without it closes by itself?

EDIT: I noticed that when it removes components with Vlite it closes by itself, if you add drivers, we made adjustments, there'll have no problems ...

This post has been edited by bapt: 24 February 2011 - 12:50 PM

[romantiq]

The question is : removing WHAT component(s) generates Vlite crash ? Some components of SP1 have something particular : another architecture, different dependencies ? But why in MSDN kit only? Questions ...

[bapt]

The question is : removing WHAT component(s) generates Vlite crash ?

just remove "file and printer sharing (server)" generates Vlite crash...

[romantiq]

Ok, seems like Vlite causes erros in installation process by modifying files "digital signature" , so windows don't recognize files version. I think I will compare files in vlited wims from both versions of W7 SP1 (MSDN and slipstreamed). Sounds like is a crazy move, but what els can I do?

This post has been edited by romantiq: 24 February 2011 - 02:35 PM

[bapt]

I can already make a list of some .dll and files corrupt and modified

I think Vlite removes components correctly but when cleaning (just after the removal of components) that vLite crash...

[Schemek]

Hi I have been playing for quite a while now with dism scripts, vLite, RT7Lite, 7Customizer and other tools. I think that development of RT7Lite is going in the wrong direction. vLite is like a Porsche here:) I just hope it will be better in the future. Anyway good to hear that, it's not only me having problems with corrupted files during installation:) I thought it was my fault, because of deep cleaning of install.wim. Here is the list of corrupted files spotted so far:

system32

pdhui.dll polstore.dll PortableDeviceApi.dll PortableDeviceClassExtension.dll PortableDeviceConnectApi.dll PortableDeviceStatus.dll PortableDeviceSyncProvider.dllPortableDeviceTypes.dll PortableDeviceWiaCompat.dll PortableDeviceWMDRM.dll puiapi.dll rasapi32.dll rascfg.dll rasdiag.dll rasmxs.dll rasser.dll resutils.dll samlib.dll sbeio.dll sdshext.dll srclient.dll wercplsupport.dll wfapigp.dll wmi.dll wscisvif.dll wscproxystub.dll wscsvc.dll WSManMigrationPlugin.dll WsmAuto.dll wsmplpxy.dll WsmRes.dll plasrv.exe printui.exe resmon.exe ROUTE.EXE rrinstaller.exe SearchFilterHost.exe wsmprovhost.exe

wbem

NCProv.dll wbemprox.dll wbemsvc.dll WinMgmtR.dll WmiApRes.dll WMICOOKR.dll WMIsvc.dll

oobe

WinLGDep.dll winsetup.dll wdsutil.dll

setup

cmmigr.dll

shared/res

padrs404.dll padrs411.dll

Might be useful for someone.

[bapt]

thank you for this list

I will add
spwizimg.dll in SysWOW64
WinMgmt.exe in System32

Will someone an idea to make it compatible Vlite with 7 sp1 MSDN?

This post has been edited by bapt: 25 February 2011 - 05:14 AM

[alvinkhorfire]

Guys, how do you know which files are corrupted?

[monkie53]

romantiq, on 24 February 2011 - 05:01 AM, said:

I wish I tell that your - everyone - solution solved my problem, but my "lite" installation of W7 SP1 vlited fails - after first restart of installation - with a blank screen, with white text, telling me that : "Windows fails to start" with error code 0xc0000428, "Windows cannot verify digital signature of file : C:\Windows\System32\winload.exe",

Yes I tested the x86 version and yes issues with the winload.exe is corrupted when using Vlite and x86 MSDN SP1 , do the same thing to the x86 as I stated above in changing date/time for all
( Date Created, Date Modified, and Date Accessed ) will fix the issues, it did for me.

I have fixed my ISO files, they now werk fine with Vlite and are the same files except the date changes were changed to July 13 2009.

Mounting the install.wim is easy with GimageX, take ownership of the winsxs folder is really a hard issue if you do not know how the "easy" way..

here is a simple ( source code found in google ) change folder date time I used

source code included - .exe in main folder to use ( needs Visual Basic 6 application to use the source code, for those that needs to know this )
 Change_Folder_Date_Time_Code.7z (9.25K)
Number of downloads: 106

here is my right click take own reg tweak I have been using for over a yr now..

NOTE: You have to take ownership of the winsxs folder before you can change the date on this folder as You do not have *access rights to modify it*

NOTE 2: running take ownership of the winsxs folder when mounted will take some time ( 10 ~15 minutes or more *depends on Your PC speed* ) so be patient with this step

Windows Registry Editor Version 5.00

;Add "Take Ownership" to context menu ( This one will do many folders deep unlike the other one )
[HKEY_CLASSES_ROOT\*\shell\takeownership]
@="Take Ownership"
"HasLUAShield"=""
"NoWorkingDirectory"=""

[HKEY_CLASSES_ROOT\*\shell\takeownership\command]
@="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"
"IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"

[HKEY_CLASSES_ROOT\exefile\shell\takeownership]
@="Take Ownership"
"HasLUAShield"=""
"NoWorkingDirectory"=""

[HKEY_CLASSES_ROOT\exefile\shell\takeownership\command]
@="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"
"IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"

[HKEY_CLASSES_ROOT\dllfile\shell\takeownership]
@="Take Ownership"
"HasLUAShield"=""
"NoWorkingDirectory"=""

[HKEY_CLASSES_ROOT\dllfile\shell\takeownership\command]
@="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"
"IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"

[HKEY_CLASSES_ROOT\Directory\shell\takeownership]
@="Take Ownership"
"HasLUAShield"=""
"NoWorkingDirectory"=""

[HKEY_CLASSES_ROOT\Directory\shell\takeownership\command]
@="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t"
"IsolatedCommand"="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t"

[HKEY_CLASSES_ROOT\Directory\shell\runas\command]
@="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t"
"IsolatedCommand"="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t"

This post has been edited by monkie53: 25 February 2011 - 06:43 AM

[bapt]

monkie53, on 25 February 2011 - 06:35 AM, said:

Yes I tested the x86 version and yes issues with the winload.exe is corrupted when using Vlite and x86 MSDN SP1 , do the same thing to the x86 as I stated above in changing date/time for all
( Date Created, Date Modified, and Date Accessed ) will fix the issues, it did for me.

I have fixed my ISO files, they now werk fine with Vlite and are the same files except the date changes were changed to July 13 2009.

Mounting the install.wim is easy with GimageX, take ownership of the winsxs folder is really a hard issue if you do not know how the "easy" way..

here is a simple ( source code found in google ) change folder date time I used

source code included - .exe in main folder to use ( needs Visual Basic 6 application to use the source code, for those that needs to know this )
Change_Folder_Date_Time_Code.7z

here is my right click take own reg tweak I have been using for over a yr now..

NOTE: You have to take ownership of the winsxs folder before you can change the date on this folder as You do not have *access rights to modify it*

NOTE 2: running take ownership of the winsxs folder when mounted will take some time ( 10 ~15 minutes or more *depends on Your PC speed* ) so be patient with this step

Windows Registry Editor Version 5.00

;Add "Take Ownership" to context menu ( This one will do many folders deep unlike the other one )
[HKEY_CLASSES_ROOT\*\shell\takeownership]
@="Take Ownership"
"HasLUAShield"=""
"NoWorkingDirectory"=""

[HKEY_CLASSES_ROOT\*\shell\takeownership\command]
@="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"
"IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"

[HKEY_CLASSES_ROOT\exefile\shell\takeownership]
@="Take Ownership"
"HasLUAShield"=""
"NoWorkingDirectory"=""

[HKEY_CLASSES_ROOT\exefile\shell\takeownership\command]
@="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"
"IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"

[HKEY_CLASSES_ROOT\dllfile\shell\takeownership]
@="Take Ownership"
"HasLUAShield"=""
"NoWorkingDirectory"=""

[HKEY_CLASSES_ROOT\dllfile\shell\takeownership\command]
@="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"
"IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrators:F"

[HKEY_CLASSES_ROOT\Directory\shell\takeownership]
@="Take Ownership"
"HasLUAShield"=""
"NoWorkingDirectory"=""

[HKEY_CLASSES_ROOT\Directory\shell\takeownership\command]
@="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t"
"IsolatedCommand"="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t"

[HKEY_CLASSES_ROOT\Directory\shell\runas\command]
@="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t"
"IsolatedCommand"="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrators:F /t"

hello monkie53

thank you for your great work

if I understand it, take possession on the "windows" and "winsxs" folder (when mounted install.wim with Gimagex example), and apply your patch, right?

thank you very much