Oops, I didn't mention, it's a brand new clean Windows installation. It never had Office installed before. Edit: but you know what? I'm going to try it and luckily it will work. I got nothing to lose besides I have an image of C drive in case I need to start anew. Edit2: running it right now... Clicked y and it's cleaning something right now.... Finished and restarting machine... Okay, at least this path is gone C:\Program Files\Common Files\microsoft shared\ClickToRun\ as expected. Now running setup once again and... nope it didn't work.
Trying this out right away and it's working so far... Installing Microsoft 365 Enterprise based on a package containing: Office_16.0.14931.20132_x86x64_es-ES_Monthly_W11_W10_w81 from March 22, 2022. Dunno whether this package I downloaded yesterday is corrupted or something has changed courtesy of MS Office_16.0.15225.20288_x64_es-ES_Monthly_W11_W10_w81 Edit: Microsoft 365 installed along with Project 2021 Yay
Similar frustration here - install (or upgrades) hangs at 50% with "Problem streaming Office, try again later. Error Code: 30015-25 (1392)" when performing a local install/upgrade of June's "us_EN" 16.0.15128.20280 on W10 21H2 using YAOCTRI. A cleanup with "SetupProd_OffScrub.exe" followed by fallback/reinstall of May's 16.0.15028.20248 for the same via reinstall with YAOCTRI and all is well again. Same if using OfficeScrubber_8. Pulled in a local copy of 16.0.15128.20280's "stream.x64.x-none.dat" twice, the SHA256 remains: 6bec482a6a9b276ac0c097dbe170849573813343fb693a3c0efb2d630a9198e1 Update: Retrieved "stream.x64.x-none.dat" a third (and 4th) time, both SHA256 hashed as: 8f52fe3fd2dd9c38936cfc9fc2bd9b209e735967d6f47b51fac8cc383c817d1b. Successfully completed installation via YAOCTRI. Not sure where this "corruption" occurred. The likelihood of remote read, transient, or local write corruption resulting in the same SHA256 hash for the same file, retrieved on two different machines at two different times is extremely low. Suspect that Microsoft's OfficeCDN file (or a cached CDN instance) may have been corrupted.
When I update Office 2019, "There's a problem with your Office license" is displayed. I'm using Windows 11.
@Zenkaino lovelive : happy to know that your problem is solved ... but how ? Can you share your experience (= explain your problem + your solution) such that other people can benefit from it ? Thanks in advance, Bill
Thank you, ratzlefatz! This worked great for my retail 2016 install. The only problem I have is that it installed some things I didn't expect. I may have missed the option to prevent the install as I was going through the interface. Good way to get rid of them?
Hi. How can I do this above on the quote? (Install Office 2016 and then licenses for Office 2019 and 2021, so that I can have Office 2021 features on Windows 7) Can anyone help? Thanks in advance!
Office 2021 is not compatible with Windows 7 you can only have Office 2019 use YAOCTRI to install Office 2019 volume, it have the workaround or install Office 2016 Retail yourself, then use C2R-Retail2Volume to convert licensing to Office 2019
Thank you for the reply! I didn't know Windows 7 couldn't have Office 2021. Good to know. Also read that on the readme of your Retail2Volume script saying it can be installed but won't work properly. Interesting. I was thinking it would be compatible for more time. Anyway, thank you. About running the script, I installed Office 2016 as you said (can't install Office 2019... screwed up something, now says "Something went wrong" - might be due to having tried 2021 before it while I had 2019 installed as a plus...), and ran the script (v16 AIO) right after the setup closed. It says: Code: ProPlus 2016 Suite -> ProPlus 2016 Licenses Office16ProPlusVL_KMS_Client It doesn't say it converted to 2019 volume licenses. Did it do it? Or I missed something somewhere? From the readme, I understood that I just had to run it and that was it. Though it also says there what happens for Win8, 8.1 and 10, it doesn't say what happens on Win7, so not sure if I can proceed to activate it or it's not ready yet. Thank you again.
@DADi590 What's your installed Office 2016 source? you apparently used the old (RTM) iso, it doesn't have or support Office 2019 use Office Deployment Tool, or YAOCTRU to download latest build for Win7 from Current / Monthly channel then use YAOCTRI
Ah then now I understand why sometimes I could install various Office versions from one installer alone, and I think that also explains why I cannot install the Office 2019 source I have (I deleted the one I used to use, which worked - now this one doesn't, and seems it's above the max version for Win7). And yes, I was using the minimum version the script works on (16.0.9029.2167). Thank you! Ok, so I have downloaded the latest version with the U script and I've installed it. Though I must have done something wrong, because it's saying it will only receive security updates. Here's what's on the INI I used through YAOCTRI: Code: [configuration] SourcePath="C:\Users\DADi590\Transferencias\YAOCTRU_v8.2\C2R_Monthly" Type=Local Version=16.0.12527.22197 Architecture=x64 O32W64=0 Language=pt-PT LCID=2070 Channel=Monthly CDN=492350f6-3a01-4f97-b9c0-c7c6ddf67d60 Suite=ProPlus2019Volume ExcludedApps=Groove,Lync,OneDrive,Teams UpdatesEnabled=True AcceptEULA=True PinIconsToTaskbar=False ForceAppShutdown=True AutoActivate=False DisableTelemetry=True DisplayLevel=True AutoInstallation=False What should I correct there? Does it help if I say that Control Panel says this is Office 365 ProPlus (weird description there. always is the complete name, Professional Plus). But Office itself says it's Office 2019 Professional Plus. Why does Control Panel say it's 365? (Unless that's supposed to happen?) Also, I read on Wikipedia that Office 2019 Retail goes up to version 2206 and Volume goes up to 1808. Should I install first as Retaill, update it and then convert to Volume and activate? (Though my current attempt says it's on version 2002, which is already higher than 1808, but still very much lower than 2206.) PS: a licensing program says this: Code: LICENSE NAME: Office 16, Office16O365ProPlusR_Grace edition LICENSE DESCRIPTION: Office 16, RETAIL(Grace) channel ERROR DESCRIPTION: The Software Licensing Service reported that the license is not installed. [Though, this one below is working:] LICENSE NAME: Office 19, Office19ProPlus2019VL_KMS_Client_AE edition LICENSE DESCRIPTION: Office 19, VOLUME_KMSCLIENT channel PS 2: about this just above. There was a notice on Office asking me if I wanted to activate the Office 365 installation (which I didn't know I had) because it had more features than the current installation. I said yes. Maybe that's why Control Panel says it's 365, not sure (didn't check before saying yes). Should I have said no? (No problem on that, I've uninstalled Office on this thing maybe 7 or 8 times, I can do it 7 or 8 more until I get it right.)
@DADi590 - Yes, Win7 only gets security updates (Office 2019 features should already work) - Yes, it's expected the installed SKU is "Office 365 ProPlus", which is fine - PerpetualVL2019 channel source is not compatible with Win7, and it's locked on Version 1808 for good) the higher Version for Retail channel source doesn't mean extra features - Office C2R on Win7 is locked on Version 2002 any higher Version is not compatible - That Office16O365 grace redundant has no effect, you can ignore
About the last thing, just before you said this, I remembered I had to first convert to Volume. So I did, and reactivated. Office now says it's Mondo 2016, even though it has Office 365 also on it because it has the Auto Save toggle, and starts as Word Office 365, and still says the same on the Control Panel. No bad thing about that, right? All seems to work anyway. I didn't know Windows 7 couldn't update more than some version, I thought it only could not install above some version, but not update (but maybe that doesn't make much sense, not sure). So highest version forever on security updates until they stop them. Cool for me! Also interesting to know Office 2019 is compatible with Windows 7 until a certain update (or better said, I guess, Office 16 is compatible until a certain update). Thank you so much for your help!