Windows 8-10, Office 2013+ use SPP, which is built-in Windows service. Between that hook (Image Exectution Options), activation/renewal is automatic. Only W7 / Office 2010 would need special task/etc for renewals as they need their own service.
Hmm.. it should be there. Maybe things changed EDIT: Just looked at the code. It seems that he implemented it even for Windows 7 / Office 2010 (which doesn't use SPP rather Office service). It uses same IFEO (see lines 143-147). I *think*... Guess wait for abbodi or someone else EDIT2: @BALTAGY See this and this. There are a few more relevant posts, search for "2010" by member abbodi1406. But this should suffice.
I activated Win10 1809 then installed office 2019 and without running 2-Activate-Local.cmd or reboot it's activated But not sure if it will auto renew after 1d ( time i edited ) both system and office ? Also if activating office in win7 is same story ?
Autorenewal is works in two parts: - KMS IP/port better set with WMI can be set directly through registry for Office 2013/2016/2019 on Windows 8/8.1/10, it use the same sppsvc settings for Windows itself, so once OS is KMS activated, Office will auto activate too Code: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\SoftwareProtectionPlatform] KeyManagementServiceName KeyManagementServicePort for Office on Windows 7, or Office 2010, it use the osppsvc settings which does not exist by default, so the script manually adds them whether Office installed or not Code: [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\OfficeSoftwareProtectionPlatform] KeyManagementServiceName KeyManagementServicePort - Image File Execution Options which allow the hook to take over file responsible for KMS activation/reactivation Code: SppExtComObj.exe for Windows 8/8.1/10 SppExtComObj.exe for Office 2013/2016/2019 on Windows 8/8.1/10 sppsvc.exe for Windows 7 osppsvc.exe for Office 2010 on Windows 8/8.1/10 osppsvc.exe for all Office on Windows 7 the hook then work as internal KMS server, it intercept the request and write activate response -- using external (online) KMS server will only require the first part == osppsvc use registry to store and control renewals Code: [HKEY_USERS\S-1-5-20\Software\Microsoft\OfficeSoftwareProtectionPlatform] VLRenewalSchedule
Hello I'm attempting to add language packs to Windows 10 1809 Build 177631.180914.1434.RS5. I keep getting an error telling me that it was unable to find install.wim. The screen shots are below. Spoiler: W10MUI.cmd ERROR Spoiler: ISO Image with install.wim I would appreciate any and all help with this issue. If you need more information, please do not hesitate to ask. Thank You.
You can't service an install.wim inside a mounted iso. Use the extracted iso path (advised) or put the install.wim next to W10MUI script. ps, adding that many LP's will increase the footprint of the install big time.
@vze2mp9g either extract/copy you iso to c:\iso and set that folder as target or set mounted drive G: as target or place .iso file next to W10MUI.cmd and it will be detect and set automatically p.s. no need to quote thw whole first post @Enthousiast the script copy the mounted iso to work directory similar to extracting the iso file
Thank you. I had the ISO in the C:\ISO, then I copied the W10MUI project in the C:\ISO\ folder and everything worked fine. You made me very happy! Will the W10MUI work on a multi arc (x86 + x64) ISO?
i added the store back successfully using the "Add-Store 17763" script but it doesn't seem to work. I can see software in the store but get an error anytime I hit the get button. Could it be that I don't have Enterprise edition software? I'm also not familiar with the, "Media Feature Pack for Enterprise LTSC N edition" like where you get it and how do you install it?
https://support.microsoft.com/en-us/help/4134255/media-feature-pack-for-windows-10-n-october-2018 you better use normal edition LTSB
I apologisze for my ignorance but I'm having trouble breaking the code. I see only two versions.... Add-Store 17763 0.1 Add Microsoft Store to Windows 10 Enterprise LTSC 2019 Add-Store 14393 0.1 Add Microsoft Store to Windows 10 Enterprise LTSB 2016 Nevermind, seeing them in my post made me realize one was LTSB and the other LTSC... Thanks. ps... I am puzzled with the media pack requirement, looks like it adds back many of the features we worked so hard to get rid of. Am I seeing this wrong?
Works exactly the same, I can pull up the store but get an error when I hit "get" to download any app.
Hi @abbodi1406, First of all, thanks for all your tools. I was wondering if you plan to include support in W10UI for: Driver injection into install.wim Adding users own tweaks via reg file to mounted hive Thanks!
I have 10586.0 Pro OEMRET ESD for digital license (HWID) purposes. ESD decrypter v37: ESD decrypter v43: