• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
bapt

[SOLVED] problem with Vlite 1.2 and Win7 SP1 (MSDN)

189 posts in this topic

Than you can change the date of winsxs folder, no ? I hope for you, my brain is on fire and I decide to watch some movies just to forget about painfull SP1 (I have the impression that Microsoft plans to release his own Lite Edition and vlite performances looks like an unwanted competition).

0

Share this post


Link to post
Share on other sites

Sorry its being a pain for you bapt, not sure what else it could be on the take ownership.

ahh possible that your Administartor account is not Administrators and is actually Administrator

if so then take ownership may fail

or better yet here is the reg file with just administrator

try this to see if it werks..


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 administrator:F"
"IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrator: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 administrator:F"
"IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrator: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 administrator:F"
"IsolatedCommand"="cmd.exe /c takeown /f \"%1\" && icacls \"%1\" /grant administrator: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 administrator:F /t"
"IsolatedCommand"="cmd.exe /c takeown /f \"%1\" /r /d y && icacls \"%1\" /grant administrator:F /t"

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

I tested 2 versions in x86 so far by doing this and it does werk on it also as both Starter and Home Basic now are able to be modded in Vlite and no corruption on install.

I am sure there is a easier way to get around this, but until its all werkd out and a simpler guide is created I'll keep at it until someone can say it workd for them.

And Yes ONLY the winsxs folder needs take ownership ran on it , the Windows folder you can change date time right after mounting the .wim file

Only Windows and winsxs folder needs attention, no other folders from my results.

EDIT: ok for the x86 do the system32 folder too then see if that does the trick, imma getting ready to do the x86 Home Premium so I'll post what I do for it to werk in a few ( hour or so )

Edited by monkie53
0

Share this post


Link to post
Share on other sites

I tested other software to change the date and time

I set 13/07/2009 and 20h20mn00s for winsxs and all contents of winsxs

Some folders in winsxs are to 14/07/2009 (I know not why)

save the change, and unmount install.wim

reboot and mount install.wim with gimagex and the .dll, .exe files are still corrupted ...

I'm testing on a x64...

after, why changing the date of winsxs, Vlite that will be compatible?

I tested with Windows 7 and sp1 integrated, "date modified, etc...." are not changed and it works very well

and the "creation date" is the same (creation date: 14/07/2009) for 7 sp1 MSDN and 7 sp0 and sp1 integrated

thank you to explain ;)

EDIT: after I tested on a install.wim where I customize some dll (imageres, etc. ...)

but no problem with windows 7 and sp1 integrated

Edited by bapt
0

Share this post


Link to post
Share on other sites

I tested other software to change the date and time

I set 13/07/2009 and 20h20mn00s for winsxs and all contents of winsxs

Some folders in winsxs are to 14/07/2009 (I know not why)

save the change, and unmount install.wim

reboot and mount install.wim with gimagex and the .dll, .exe files are still corrupted ...

I'm testing on a x64...

after, why changing the date of winsxs, Vlite that will be compatible?

I tested with Windows 7 and sp1 integrated, "date modified, etc...." are not changed and it works very well

and the "creation date" is the same (creation date: 14/07/2009) for 7 sp1 MSDN and 7 sp0 and sp1 integrated

thank you to explain ;)

EDIT: after I tested on a install.wim where I customize some dll (imageres, etc. ...)

but no problem with windows 7 and sp1 integrated

did you get to run the takeown successfully on the winsxs folder?? this maybe the issue if not even with a program changing the folder date ( just guessing here )

0

Share this post


Link to post
Share on other sites

did you get to run the takeown successfully on the winsxs folder?? this maybe the issue if not even with a program changing the folder date ( just guessing here )

I removed the protection on any files contained in winsxs (and also winsxs) with software to modify the attribute, and I changed the date of winsxs and all content

I used vLite, reboot and mounted install.wim with gimagex

winsxs is the date of 13/07/2009 (the 3 dates) and all content winsxs also and I always corrupt files

0

Share this post


Link to post
Share on other sites

Monkie53, I used an imagex batch (attached) which includes the ownership part for mounting install.wim, then I used a third party program to modify date. I verified in every moment files attributes just to be shure that the date is 07/13/2009 (all 3 dates). Even in final vlited ISO. I applied date modifications to ENTIRE Windows folder including subfolders (and , of course, including winsxs folder). But winload error is still there. I will try your application and i will modify dates in windows (without subfolders) and winsxs only (like you sayed). And I will use gimagex too ...

This will not work as Install Wim Tweak is for taking ownership of the reg hives in the install.wim so you can Remove Packages and such, it will work for that and that only.

This has to be done by a take ownership as I did, no application is going to work, this is a winsxs folder MS has locked all these files down hard, so applications to do it in just a few seconds will not work here, nor will using the windows Security - Permissions setting native buildt into windows as I tried that last night also, even though I can do it and use the Change Folder Date Time.exe it still corrupts the files so even MS's own Permission tools sux here.

Its all about getting that take own to work, thats all that has worked for me so far out of all the things posted here.

I have a feeling its a Language barrier with the reg tweak I posted and the Change Folder Date Timexe.exe, I dont know how to work with these issues to get a working solution if this is the case.

after appling the reg tweak I posted does the language change to Your native language or how does these things work in say French windows environment?? I am clueless here..

Is there any native English users here that can try this and say if it works for them or not?? that would be a help, dont know how but I think if someone else can get it to work that would be a good thing.

I'll check back later today, as today is a busy one for me.

0

Share this post


Link to post
Share on other sites

I tried this on x64 Ultimate and it didn't work either. I get the errors after install.

0

Share this post


Link to post
Share on other sites

I've tested with a "take ownership" that works, Monkie53'software (to change the date) does not work for me (error message)

I used another software, changed the 3 dates "winsxs" folder (and contents) on 13/07/2009 and that's OK with vLite, no problem :thumbup

I also change the date of the "windows" folder (not contents) on 14/07/2009

is what to do or not?

0

Share this post


Link to post
Share on other sites

i think i may have found a workaround. i successfully installed msdn sp1 x86 after vlite removal. will post details after some more testing and a nice hot bath :P

Edited by dead0
0

Share this post


Link to post
Share on other sites

i think i may have found a workaround. i successfully installed msdn sp1 x86 after vlite removal. will post details aftesome more testing and a nice hot bath :P

ok thank you for your feedback ;)

0

Share this post


Link to post
Share on other sites

ps can someone try this for me:

1) ensure u have waik 2.0 installed as u will need imagex from that

2) mount install.wim with imagex, u do not need to do anything such as add or remove files

3) unmount wim with commit changes

4) run vlite, make sure u have wimgapi.dll & wim filter from vista waik

let me know the outcome

43387324.jpg

testinstalls20110227161.png

0

Share this post


Link to post
Share on other sites

you can not use Gimagex? must mount "install.wim" with imagex of the WAIK 2.0?

and just need to mount (do nothing) and unmount the image with commit change (we have not done)?

then run Vlite "normal" is that all?

thanks ;)

Edited by bapt
0

Share this post


Link to post
Share on other sites

you can not use Gimagex? must mount "install.wim" with imagex of the WAIK 2.0?

and just need to mount (do nothing) and unmount the image with commit change (we have not done)?

then run Vlite "normal" is that all?

thanks ;)

yes thats all.

u can use gimagex but make sure its the latest version

0

Share this post


Link to post
Share on other sites

it's Gimagex 2.0.17, it's good?

if you just mount/unmount install.wim, is really simple :lol:

I tested With Gimagex ;)

0

Share this post


Link to post
Share on other sites

my guess its the wimfilter that is corrupting the image. when you're mounting/dismounting with gimagex (or imagex), make sure the wimfilter is from waik 2.0 or win7. then u can install the vista waik wimfilter for vlite...? when dismounting, it should take around 20 minutes to complete

Edited by dead0
0

Share this post


Link to post
Share on other sites

I tested with Gimagex, and it works not

after using vLite, there are corrupt files

when I used Gimagex is the wimfltr.sys (windows\system32\drivers) of Vista I think

I used Vlite "normal", with wimgapi and wimfltr.sys files (6.0 6001 18000) for Vista

is not good?

EDIT: OS of the PC where I'm testing is a 7 x64 (sp1 integrated)

Edited by bapt
0

Share this post


Link to post
Share on other sites

i just did another test & no errors after vlite

u could try this way:

1) ensure waik 2.0 is installed

2) in cmd prompt, go to Program Files\Windows AIK\Tools\amd64 and execute wimmountinstall /install

3) copy wimmount.sys from above folder to Program Files (x86)\vLite\wimfltr\x64

4) rename wimfltr.sys (this is the vista version) to something else such as wimfltr2.sys as you will need it later

5) rename the copied wimmount.sys to wimfltr.sys

6) right click wimfltr.inf Program Files (x86)\vLite\wimfltr\x64 folder to install

7) using gimagex or imagex, mount install.wim and then dismount wim with commit changes. this should take a while around 20 minutes depending on pc. u should only need to do this once to a wim unless u start from afresh

8) go back to the vlite wimfltr folder and rename wimfltr2.sys to wimfltr.sys (also rename wimfltr.sys back to wimmount.sys)

9) right click wimfltr.inf and install again. this will copy the vista version back to system32\drivers

10) use vlite

u may need to switch between the 2 filters when using imagex and vlite

Edited by dead0
0

Share this post


Link to post
Share on other sites

I'll try this ;)

wimmount.sys of the WAIK3 is not good?

0

Share this post


Link to post
Share on other sites

I'll try this ;)

wimmount.sys of the WAIK3 is not good?

i used wimmount from waik 2. i dont think there is any difference between the two

it seems sp1 is tightly locked down when compared to the non sp version

Edited by dead0
0

Share this post


Link to post
Share on other sites

with the wimmout.sys of WAIK3, imagex and gimagex does not run (error)

with WAIK2 (Automated Installation Kit (AIK) for Windows Vista SP1 and Windows Server 2008) there is no file wimmout.sys (just wimfltr.sys)

and it is the same as that used with vlite

Edited by bapt
0

Share this post


Link to post
Share on other sites

with WAIK2 (Automated Installation Kit (AIK) for Windows Vista SP1 and Windows Server 2008) there is no file wimmout.sys (just wimfltr.sys)

and it is the same as that used with vlite

WAIK 2 is for 7 I thought. 1.1 is for vista. 1.1 was released in 2008, 2 was released in 2009 and 3 this month. WAIK 2 should have the wimmount.sys, that is what I have.

0

Share this post


Link to post
Share on other sites

i just did another test & no errors after vlite

u could try this way:

1) ensure waik 2.0 is installed

2) in cmd prompt, go to Program Files\Windows AIK\Tools\amd64 and execute wimmountinstall /install

3) copy wimmount.sys from above folder to Program Files (x86)\vLite\wimfltr\x64

4) rename wimfltr.sys (this is the vista version) to something else such as wimfltr2.sys as you will need it later

5) rename the copied wimmount.sys to wimfltr.sys

6) right click wimfltr.inf Program Files (x86)\vLite\wimfltr\x64 folder to install

7) using gimagex or imagex, mount install.wim and then dismount wim with commit changes. this should take a while around 20 minutes depending on pc. u should only need to do this once to a wim unless u start from afresh

8) go back to the vlite wimfltr folder and rename wimfltr2.sys to wimfltr.sys (also rename wimfltr.sys back to wimmount.sys)

9) right click wimfltr.inf and install again. this will copy the vista version back to system32\drivers

10) use vlite

u may need to switch between the 2 filters when using imagex and vlite

This is interesting. I thought I had something wrong with my pc after all the uninstall and install of these components yesterday when it took that 20min to work with waik2. I thought I tried something similar because I was trying different things with vlite and the filters. I just tried this and didn't get the winlogon error but did get an error with installing some components. Might be my vlite session. Can you post your session you are using to achieve this and I will try? This might be the reason the regtweak doesn't work either is because of the filter version.

0

Share this post


Link to post
Share on other sites

WAIK 2 is for 7 I thought. 1.1 is for vista. 1.1 was released in 2008, 2 was released in 2009 and 3 this month. WAIK 2 should have the wimmount.sys, that is what I have.

WAIK 1.1 => WAIK for Windows Vista

WAIK 2 => WAIK for Windows Vista SP1 et Windows Server 2008

WAIK3 => WAIK for Windows 7

not wimmount.sys on WAIK 2 ;)

Edited by bapt
0

Share this post


Link to post
Share on other sites

WAIK 2 is for 7 I thought. 1.1 is for vista. 1.1 was released in 2008, 2 was released in 2009 and 3 this month. WAIK 2 should have the wimmount.sys, that is what I have.

WAIK 1.1 => WAIK for Windows Vista

WAIK 2 => WAIK for Windows Vista SP1 et Windows Server 2008

WAIK3 => WAIK for Windows 7

not wimmount.sys on WAIK 2 ;)

Thanks for clarifying, Than it doesn't make sense what dead0 is saying.

0

Share this post


Link to post
Share on other sites

when "ownership"in the winsxs folder and its contents, it is the owner

is that possible to "TrustedInstaller" as owner after the change?

thanks ;)

Edited by bapt
0

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.