© KEiGHT
-
Posts
248 -
Joined
-
Last visited
-
Days Won
2
Content Type
Profiles
Forums
Events
Posts posted by © KEiGHT
-
-
there's no need for that folder, just delete it !
-
It is a .cab file ?
-
Liam, can we get an result of this issue today ?
If you are busy with Study just I bag your pardon !
WinToolkitRunOnce.exe has an issue on x64 to start !
-
It also happened in 1.4.38.8, too.
-
Why Change Setup Background was Removed from the TWEAKS ?
later edit: It was disappear because I manage only WIM file , sorry
-
NO is NOT Working ! I use 1.4.38.8 and is NOT from Services ! Has nothing to do with them !
-
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?
-
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 !
-
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 !
-
Install Shield, installing what ? is an .exe right?
Try -s
-
NO, does not work even with that enabled ! :doh:
-
Yes but I guess Application management service is responsible with run of WinToolkit because don't work even with the latest build
-
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.
-
Ok , I will check this out , Thanks mate !
-
Which are those services?
-
I saw that on last compilation .. pff, I will start again with all-in
the problem is , cuz none of the updates was installed if I don't specified to be integrated even those are integrated before! That's a big mistake I guess !
-
Does not start RunOnce neither with this ! pff
Liam, did you modified the Install.ini at => INSTALLDIR=???
my example :
00004| 04 Adobe Flash Player ActiveX 13.0.0.214 |%DVD%:\WinToolkit_Apps\04_Adobe_Flash_Player_ActiveX_13.0.0.214\Adobe_Flash_Player_ActiveX_13.0.0.214.exe*-install
is there any fault if I put numbers in front of apps like we see up in that line? in x86 it works in any case !
-
nope, but I have a question till I find it myself !?
if just I manage to load in the compiler without adding any other stuff or loading presets, the program will keep all my stuff added before, right ?
Right now I do this experiment !
-
won't work in that way ! :shifty:
-
Good Morning fellows,
If I just open the wim image with the last version and save image in wim registry editor, will work ?
-
[Config]
INSTALLDIR=%DVD%:\WinToolkit_Apps
DRIVERDIR=Sources\Drivers
REBOOT=TRUE -
yes, today ! but still got the same issue... it skip RunOnce !
the config is the same as always ? or is modified ?
this is mine which is working in x86 but not in x64
[Config]
INSTALLDIR=%DVD%:\WinToolkit_Apps
DRIVERDIR=Sources\Drivers -
Hi Liam,
it's kind of strange thing, because in x86 it works, only with x64 does not !
-
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]
[Solved] Win Tool kit run once installer in win 7 64 bit
in WinToolkit Solved Bugs
Posted
1.4.37.15^FIX: RunOnce Installer not working when certain updates added
is this bug back again with x64?