What is the difference between the smart activation script and windivert? I use w7 and 10(occasionally), i dont use Office.
Both are smart activation scripts for Win7 no real difference the difference is for Win8.1 & Win10, because Localhost IP can't be used directly for KMS activation a workaround is needed to "bypass" that Windivert uses packet redirection, and it need external KMS server emulator (vlmcsd.exe) SppExtComObjPatcher uses DLL injection method, and it has internal KMS server emulator functions this also allow to install it as Debugger, so the system itself launch it and reactivate when needed
Hi , abbodi I love you I use yours scripts for activations office ... good work for several years. great thanks !
How can I make the output of this command cscript //nologo ospp.vbs /dstatus go to a message vbs like cscript /nologo %tmp%\tmp.vbs
I'm not expert in vbscript, but i believe that's a limitation in ospp.vbs it would require another vbs to read output from text file to message box something like: Code: @echo off cd /d "%ProgramFiles%\Microsoft Office\Office16" cscript //nologo OSPP.VBS /dstatus| findstr /b /i /v "^-" >"%systemroot%\temp\ospp_msgbox.txt" ( echo Set fso = CreateObject^("Scripting.FileSystemObject"^) echo Set objFile = fso.OpenTextFile^("%systemroot%\temp\ospp_msgbox.txt",^1^) echo tempData = objFile.readAll^(^) echo objFile.Close echo MsgBox tempData )>"%systemroot%\temp\ospp_msgbox.vbs" cscript //nologo "%systemroot%\temp\ospp_msgbox.vbs" del /f /q "%systemroot%\temp\ospp_msgbox.*"
I'm having difficulties applying latest CU 1806 to WS 1607. CoreOS-revison stays at =10.0.14393.0 I did realize when running WU that it first applies 1805 CU then after reboot it can apply 1806 CU. could that be the reason? Code: Running W10UI v4.8 ============================================================ ============================================================ Extracting files from update cabinets (.cab) *** This will require some disk space, please be patient *** ============================================================ 1/4: Windows10.0-KB4093110-x64.cab 2/4: Windows10.0-KB4093137-x64.cab 3/4: Windows10.0-KB4284833-x64.cab 4/4: Windows10.0-KB4287903-x64.cab ============================================================ Mounting install.wim - index 1/1 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17134.1 Mounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Checking Updates... ============================================================ ============================================================ Installing updates... ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17134.1 Image Version: 10.0.14393.2182 Processing 1 of 1 - Adding package Package_for_KB4287903~31bf3856ad364e35~amd64~~10.0.1.0 [==========================100.0%==========================] The operation completed successfully. Deployment Image Servicing and Management tool Version: 10.0.17134.1 Image Version: 10.0.14393.2182 Processing 1 of 1 - Adding package Package_for_RollupFix~31bf3856ad364e35~amd64~~14393.2339.1.8 [==========================100.0%==========================] Error: 0x800f081e The specified package is not applicable to this image. The DISM log file can be found at C:\WINDOWS\Logs\DISM\dism.log ============================================================ Unmounting install.wim - index 1/1 ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17134.1 Image File : C:\1607\install.wim Image Index : 1 Saving image [==========================100.0%==========================] Unmounting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Rebuilding install.wim ============================================================ Deployment Image Servicing and Management tool Version: 10.0.17134.1 Exporting image [==========================100.0%==========================] The operation completed successfully. ============================================================ Removing temporary extracted files... ============================================================ ============================================================ Finished ============================================================ Press any key to exit.
KB4284880 & KB4284833 & all future CU require SSU KB4132216 do you have it integrated? you may share dism.log if you still have it
Some questions, SppExtComObjPatcher method can activate later installed office automatically, i suppose office activation requires key inserting, so how it can activate later installed office when there is no 2-Activate-Local.cmd available? is it possible to auto activate later installed office if online method used in your script? is it possible to auto activate later installed office using windivert method? thanks.
- Volume Office should already have GVLK inserted during installation and a proper converted C2R retail2volume should also install GVLK during conversion so what's left is that Office detect the registered KMS IP address and activate against - Yes, as long the external KMS address is working and support Office - No, windivert require running the script, because no KMS IP is registered, and that because the method require 3 external programs to complete beside the AV issues and the lack of some KMS optimizations, SppExtComObjPatcher is the best KMS emulator ever exist
I'm just curious as to why some of your scripts purposely remove the efisys_noprompt.bin and cdboot_noprompt.efi items from the \efi\Microsoft\boot folder? These two files are required for having a working no-prompt UEFI bootable ISO. Even if you remaster one, without those two files on the media, it will just throw errors until you create a new ISO. What is the reason for that line of code? ^^
AFAIK, to have working no-prompt ISO, efisys_noprompt.bin must be used in cdimage/oscdimg command and since i use the default one efisys.bin, i see no benefit of keeping the noprompt ones i'm not UEFI guy anyway, but i didn't see anyone report errors about it
Yes, that bootdata are specific to oscdimg and cdimage, that's true. It's not a big deal to me at all but after trying to figure out why those files would seem to just disappear when updating an image with your script, I finally just looked at the code itself and was curious if there was some reason that was unbeknownst to me. I will just remove that line of code, then. Thanks.