Installing with RTool I couldn't get Visual Refresh to stick in LTSC. Although it's irrelevant as it's not meant for LTSC I switched back to YAOCTRI which I'm used to and could then get visual Refresh in LTSC every time again. This post.
I've given up, irrelevant to me, won't be using LTSC. 365 (Mondo licenses) visual refresh works every time. Is there any point in forcing it on LTSC?
For me it was more convenient to get a permanent grey-market retail license and force Visual Refresh on it by write-protecting the SkuIds registry keys. It happened that I need to change the system date in the past/future to test things and then I always had to rearm KMS manual activation to open Office (did not try automatic KMS activation though)
Installed ProPlus via RTool. Activated = LTSC Ran new script - Visual Refresh first time! Update: Apologies I made an error here - corrected now. Ran Office scrubber - rebooted. Installed ProPlus via YAOCTRI - channel (0 default) in YAOCTRI Ran new script - Visual Refresh first time!
Yes I should have posted as such. Good work @rioachim - After some days of trial and error, can now have Visual Refresh in LTSC every time, well done. Credit @zucrin for the coding. As said though, Office LTSC is of no interest to me personally, just enjoyed the testing of various stuff over past days. You can have Office 365 VL activated, up to date and feature updates.
Surely can't be be long now until they roll out Visual Refresh properly in Office 365, no longer needing the registry key for experimental.
I've uninstalled only the Mondo key; Office back to LTSC with regular visuals. I've applied the new script and Office is LTSC with new visuals everytime I open Word, Excel, etc.. Thanks to all of you for helping to develop the scripts!
so which is the best for office 2021 LTSC... Visual Refresh UI [New] or Visual UI LTSC Edition With Block KEYS
ok thanks so i see that this installs the retail keys is this necessary ? so no its not needed i removed the install of the retail key and also the key clean up and it all worked fine with just using (volume activated) echo -- Install Visual UI Registry Keys call :reg_own "HKCU\SOFTWARE\Microsoft\Office\16.0\Common\Licensing\CurrentSkuIdAggregationForApp" "" S-1-5-32-544 "" Allow SetValue for %%# in (Word, Excel, Powerpoint, Access, Outlook, Publisher, OneNote, project, visio) do ( 1>nul 2>&1 reg add "HKCU\SOFTWARE\Microsoft\Office\16.0\Common\ExperimentConfigs\ExternalFeatureOverrides\%%#" /f /v "Microsoft.Office.UXPlatform.FluentSVRefresh" /t REG_SZ /d "true" 1>nul 2>&1 reg add "HKCU\SOFTWARE\Microsoft\Office\16.0\Common\ExperimentConfigs\ExternalFeatureOverrides\%%#" /f /v "Microsoft.Office.UXPlatform.RibbonTouchOptimization" /t REG_SZ /d "true" 1>nul 2>&1 reg add "HKCU\SOFTWARE\Microsoft\Office\16.0\Common\ExperimentConfigs\ExternalFeatureOverrides\%%#" /f /v "Microsoft.Office.UXPlatform.FluentSVRibbonOptionsMenu" /t REG_SZ /d "true" 1>nul 2>&1 reg add "HKCU\SOFTWARE\Microsoft\Office\16.0\Common\Licensing\CurrentSkuIdAggregationForApp" /f /v "%%#" /t REG_SZ /d "{FBDB3E18-A8EF-4FB3-9183-DFFD60BD0984},{CE5FFCAF-75DA-4362-A9CB-00D2689918AA}," ) call :reg_own "HKCU\SOFTWARE\Microsoft\Office\16.0\Common\Licensing\CurrentSkuIdAggregationForApp" "" S-1-5-32-544 "" Deny SetValue echo -- Start Word. start winword
needed, better keep it that way. I will explain. its depended on license. some type of license not support visual UI. so you must add license that support visual UI. but that create second problem, this is retail license, look here to understand more.