Where you going so fast doggy??!! Sorry, thought Loader w/No OEM Branding issue was solved but NOOOO!!! Curiously on the other hand, if I run manually the Loader exe from \\Windows\Setup\scritps it seems to be successfully installed but after reboot still inactivated but when the Loader is run from, for instance desktop, Windows finally gets activated.
What's the actual error ? Never failed here, at least when system allows it. Is the keys INI present?
@s1ave77 Afterwards all details we already saw regarding Loader activation issues and due you are far most skilled on the topic for sure you are able to ask for help with proper words / inquiries at the Loader forum, no?
s1ave77 I found a workaround most likely will be easy to implement, I believe. Look, instead of copying the Loader's files to "scripts" folder, they could be copied to the root of system drive (for instance C:\) and the script to run it from there. I run it manually from that location and activation was successful. Can you modify the script to perform such task? Please.
OK ... indeed a q'nd solution and should work . Would only need additional xcopy statement and an adapted Loader path .
Change Loader part with this: Code: :LoaderInstall cls echo -------------------------------------------------------------------------------- echo WINDOWS LOADER by Daz echo -------------------------------------------------------------------------------- echo: xcopy "%~dp0"Windows Loader.exe" /s /q "%windir%\Loader" /Y >nul "%windir%\Loader\Windows Loader.exe" /silent if exist "%windir%\Loader" rd /s /q "%windir%\Loader" >nul goto:Choice3
I noticed that too, actually I'm dealing with at this very moment, because it doesn't work as s1ave77 stated.
Finally after struggling for 3 hours hey I am a n00b/46y old, was able to manage Loader stuff this way. I think it's fine unless doggy says otherwise lol: Code: :LoaderInstall cls echo -------------------------------------------------------------------------------- echo WINDOWS LOADER by Daz echo -------------------------------------------------------------------------------- echo: md "%systemdrive%\Loader" xcopy "%windir%\Setup\scripts\Windows Loader.exe" /s /q "%systemdrive%\Loader" /y >nul xcopy "%windir%\Setup\scripts\Keys.ini" /s /q "%systemdrive%\Loader" /y >nul "%systemdrive%\Loader\Windows Loader.exe" /silent if exist "%systemdrive%\Loader" rd /s /q "%systemdrive%\Loader" >nul goto:Choice3
He only can commit: Well done Sir n00b . Nothing to add . As long as INI is copied to the Loader folder, the rd (remove directory) command will clean up after execution (no traces left). We still need to check the OEM part thoroughly to avoid unnessessary activation steps (when we don't want them) and get the CLEANUP back 'online'. Stil work in progress, some little holes left. FYI: To add a new copy line, like in the case you showed, mark the line in Notepad++ by clicking the line number and press Ctr+D to double the line and adapt the pathes afterwards ... very easy .
Thanks for the notepad++ tips. btw isn't there a better and logic way to avoid xcopy lines spawned along the script? To copy certain files within a directory. For instance: Code: xcopy "%windir%\Setup\scripts\Windows Loader.exe;keys.ini;filex1.exe;filex2.ini" /s /q "%systemdrive%\Loader" /y >nul
Not that way, but one could use a sub-folder for the Windows Loader in 'Scripts' and then copy the content of that folder with: Code: xcopy "%windir%\Setup\scripts\Loader\*.*" /s /q "%systemdrive%\Loader" /y >nul