Jump to content

[Solved] Win Tool kit run once installer in win 7 64 bit


John_95

Recommended Posts

  • Replies 65
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

i'm not sure yet. the safe preset from BlackViper disable some service that disable the runonce on x64 , but on x86 the same preset works fine.

 

i didn't have time to test one by one...

Link to comment
Share on other sites

This only could be; Application Management which works with .NET Framework, surely this could be the issue ! I will test the last version and if this is not working, I will enable Application Management Service which now is disabled! Because WInToolkit needs NET Framework 4  to work , I guess this is the trigger !

 

Application Management

 

Processes installation, removal, and enumeration requests for software deployed through Group Policy. If the service is disabled, users will be unable to install, remove, or enumerate software deployed through Group Policy. If this service is disabled, any services that explicitly depend on it will fail to start.

Edited by © KEiGHT
Link to comment
Share on other sites

Here's the run once log as requested. 

 

I don't know about you guys but the current test build works for me. 

 

I need a little help I have and install shield installer that doesn't run because i don't have the right switch what is the correct installer switch

 

i use /S to install 

 

anyways here's the file 

 

WinToolkit_RunOnce_Log.txt

Link to comment
Share on other sites

Does not work with none of these:

 

Sources\Apps

%DVD%:\WinToolkit_Apps

%SourcesDir%:\WinToolkit_Apps

%Sources%:\WinToolkit_Apps

 

I don't know what else to try, for 5 days I've tried everything, but with no results !

Edited by © KEiGHT
Link to comment
Share on other sites

in your x64 build are you messing with services? i found out that some service disable the runonce on my x64 build but the same ini used on x86 works without a problem.

 

Is nothing from Services, I've set them to default, all of them, The same result; NOT STARTING > RUNONCE !

Edited by © KEiGHT
Link to comment
Share on other sites

Hmm, it's from inside the compiler WinToolkit,

something's call the wrong answer to WinToolkit in the registry or NOT calling at all ! :g:

[HKEY_LOCAL_MACHINE\WIM_Software\WinToolkit]

 

So, RunOnce respect this registry or not?

Link to comment
Share on other sites

  • 2 weeks later...

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.




×
×
  • Create New...