In what manner does the installation of Daz loader fail? What does heavily shrunk mean? Have important activation components been removed, or is it just missing .net components? Install daz loader in a virtual machine running a regular Win 7 guest. Install with option to preserve current boot code. Find the bootwin and bootmgr files, and copy them elsewhere (eg usb drive) for safe keeping. Also dump and save the certificate and serial using the Windows Loader advanced tab. Go to your "heavily shrunk" machine. Manually install (using slmgr) the same certificate and serial that you used when you activated the virtual machine. Then copy the saved bootwin and bootmgr files to the proper location. You may need to use takeown and icacls before you can overwrite the existing bootmgr file. Reboot and your stripped down creation should be activated. There, wasn't that easy?
very heavily shrunk capn, 996 compenents plus removed with ntlite. about 1gb installed. i think the error shows as certificates did not successfully install. had chats with daz in the chat window, he gave me some pointers. daz loader needs a .net? hmm. i am trying various configurations, 1 with .net351, 1 without, depends on its use. i havnt used slmgr or icacls before. easy is relative to the end users knowledge. in my case, not that easy, but your post is easy to understand, so i will save to a text file. will reply on my progress when i do it. thank you
If you can not manually install the certificate, something rather important is wrong with your shrunken creation. I'm also not sure if the loader installation needs .net
I can see that the thread's been sort of hijacked, but just to help you out... I don't think a direct link is allowed, but MDL member murphy78 on TPB has a 26-in-1 32 and 64-bit Win10 1607 (i.e. Redstone i.e. Anniversary Update) compilation.
Correct, you cannot link but you can push the info (in bold) that can be googled. Just pay attention to what google choice you make.. e.g. Spoiler Microsoft Windows 10 Enterprise x64 14393.10 en-US Activated Info Hash: 6D9E0A3D6DAF34301C4E43E7C6DD89D90509B47F Microsoft Windows 10 Enterprise x32 14393.10 en-US Activated Info Hash: 539966C1B844A317383D2E4A611B0FABA83037B0 Microsoft Windows 10 AIO 26in1 Build 14393 v1607 x32 x64 en-US Info Hash: 84BA8E52EC0667638271F9C17CB10AA67A12838E or PM'ed
Great info. So in that case these are the ones I was talking about: Spoiler Dual Release File: Win10AIO_14393_1607_en-US_x32_x64_Dual.iso Size: 6.32 GB SHA-1: 1CCD04783D99682526AC0B294F493399B3E81FA7 x86 (32-bit-only version): Win10AIO_14393_1607_en-US_x32.iso* Size: 2.82 GB SHA-1: 21FDB721EE0A3353B51ABA8ADBE2234275C766EC x64 (64-bit-only version): Win10AIO_14393_1607_en-US_x64.iso* Size: 3.53 GB SHA-1: 7B739E555CBD361388A3E929A36A7C9EF19D89C1
ultimate or pro, either is good for me. i think you are correct about pro and ent. will try pro tomorrow.
HOSANNA it works if i run it after install. but i have an existing cmd for reg files so i need to combine the two, i dont know bats/cmds, this will take some investigating. and it works on my heavily shrunk 7. right, kms, just need to run it every 180 days, or set it to run automatically. that part i get and the read me is easy to understand. Thanks Again Nucleus
if adding things in ntlite post setup, it creates SetupComplete.cmd. but the tool has a file with the same in the same location as ntlites cmd file. hmm, bugger. so i renamed the tools SetupComplete.cmd to kms.bat and added that to ntlite post setup section. i made sure i set the call "%WINDIR%\Setup\Scripts\kms.bat" rd /q /s "%WINDIR%\Setup\Scripts" values hopefully to the correct value. so install 7 pro, 1st logon, activated! thanks again Nucleus. @echo off powercfg -h off regedit /S "%WINDIR%\Setup\Files\w7-aero-peek-disable.reg" regedit /S "%WINDIR%\Setup\Files\w7-aero-shake-disable.reg" regedit /S "%WINDIR%\Setup\Files\w7-aero-snap-disable.reg" regedit /S "%WINDIR%\Setup\Files\w7-context-menu-register-unregister.reg" regedit /S "%WINDIR%\Setup\Files\w7-cpu-parking-power-options.reg" regedit /S "%WINDIR%\Setup\Files\w7-event-viewer-show-ie11.reg" regedit /S "%WINDIR%\Setup\Files\w7-ie-welcome-screen-disable.reg" regedit /S "%WINDIR%\Setup\Files\w7-pagefile-disable.reg" regedit /S "%WINDIR%\Setup\Files\w7-prefetch-superfetch-disable.reg" regedit /S "%WINDIR%\Setup\Files\w7-shortcut-arrow-classic.reg" regedit /S "%WINDIR%\Setup\Files\w7-sleep-disable.reg" regedit /S "%WINDIR%\Setup\Files\w7-take-ownership.reg" regedit /S "%WINDIR%\Setup\Files\w7-taskbar-preview-disable.reg" regedit /S "%WINDIR%\Setup\Files\w7-taskbar-thumbnail-preview-disable.reg" call "%WINDIR%\Setup\Scripts\kms.bat" rd /q /s "%WINDIR%\Setup\Scripts" del /q /f "%0"
Not with abbodis' KMS VL All, KMS functionality is as normal and will auto renew every seven days by default (the renewal interval). See How To and Brief Explanation links in my sig, one of those leads you to qad's explanation of his SppExtComObjPatcher works. Run a manual activation and you'll see it activate (KMS works as normal). Code: slmgr /ato To integrate abbodi's solution into an ISO, just put his $OEM$ folder into sources, job done. Will be activated at first boot and thereafter renewal will occur as per normal KMS.
yep, i did put the oems folder onto the iso/usb and it worked perfectly. ive got all that, okay. now ive got a solution that works, i can put this on the back burner for a while. the thing is, i do need a .net for 1 w7 configuration, the other i dont need a .net. so i needed a solution that will work on any 7 configuration, i wont need different tools now, abbodis' KMS VL All will work on any config and if i am asked, i can recommend it thank you again Nucleus, your help has really been appreciated. also thanks yous to abbodi and those who contributed to the tool, MrX CaptainKirk eth3null and Bat1