No longer working with newer packages, perhaps they are now Office 2019? Older packages still work, and I always have a backup on me, since the Appx method takes up much less space, and is a lot cleaner overall regarding uninstallations.
hey, a noob here. Plz help me My office installer keeps getting stuck at 50% or so. i downloaded the latest "current retail version" x64, en-US. Then i used ODT setup to install to install 'Microsoft 365 Apps for Enterprise'. with onenote, skype, outlook disabled. I also didn't chose to install Visio or Project as i had no idea what they were. And then started the setup ( Start local install now). i tried rebooting, scrubbing the old office via Full_Scrub cmd file, scrubbing manually. but it's always the same. kindly help.
Thank you for your error report. After installing UWP appx bundles and updating from store I confirm this bug. I will check and come back to you. But this may take a while, as I'm short of time. Update of OfficeRTool will come. Stay tuned.
Search for and delete all installation directories and files in: ..\Office\data\ (must contain files like "v64*.cab", "stream*.dat" and other *.cab/*.cat files) This will bring back ~ 3GB which is not that much. And in case of a fresh install you need to redownload them, "Online Repair" started from control panel - programs and features will download all this, too. Better save some money for a new harddisk (less trouble).
I should've employed the appropriate words lol: "to reduce the Windows installation overall size". Disk space isn't really my problem. Problem is time. Time used at the moment of making system images to backup drive C. All that burden of "useless" files to carry by my imaging program every time I make one is crazy. So ~3GB are better than nothing in this case. Thanks for your help.
Wait a second... I couldn't find such directory. Are you joking or trolling me? lol Such directory seems to be that one found in the installation files I download using YAOCTRU
No joking or trolling from my side. You asked what files and folders can be removed after Office install. I 've assumed, you meant all the installation files not needed anymore. Yep. This was my suggestion: Removing install files to free up space.
Sigh, I know you're not trolling me. I'm just having fun. Some humor. I get it but I meant some extra useless files folders such as MSOcache on drive C. Remember?
Hello, First time forum poster so If Im doing or asking something incorrectly, please advise politely so I can comply. -My Issue, I've done a clean install of Win 10 on pc in Jan 2021 with no issues. I used KMS_VL_ALL-35 and OfficeRTool2019August03 as indicated in MDF forum successfully. Yesterday, Excel exhibits invalid license message. I tried to run OfficeRTool2019August03 but it would not open as I previously remembered it did. I came back to MDL forum and got updated OfficeRTool2021May18 but am unable to run it also. It just opens and closes in half second. I turned off antivirus but still not opening (even though antivirus did not complain). No other known issues with pc and no recent Windows updates ran since March 2021. Any ideas what is wrong or how I should troubleshoot? Thanks
Installation Tips / Special Cases Treatment STARTUP: OfficeRTool SHOWS BLANK WINDOW or CLOSES shortly AFTER UAC PROMPT Reason(s): - your Antivirus- or other Security-programm is blocking access, or - you are running OfficeRTool from root \ , or - you have Brackets "[ ]( ){ }", "&" or any other special characters in folder- and/or user-name, or - you have a Special Setup / Policy Rules active, or - you have a corrupted %PATH% statement in your system variables configuration. For more info, follow the above links and read the additional replies, too. I think I had the same issue as you, so please review the corrupted %PATH% statement
5/30/21 Thanks Dolmatov and Maxama123 for your suggestions @Dolmatov, as you suggested I went here forums-mydigitallife-net/threads/kms_vl_all-smart-activation-script.79535/page-180#post-1659178 then here infohost-github-io/office-license-is-not-genuine and used OfficeToolPlus -removed all license keys using officetoolplus - excel restarted unlicensed, closed it - restart excel - error msg excel did not start correctly, would you like to fix? yes on restart Office 19, Office19ProPlus2019R_Grace edition License Description: Office 19, RETAIL(Grace) channel Last 5 characters of installed product key: 8MBCX Error Code: 0xC004F017 Error Description: The Software Licensing Service reported that the license is not installed. - used officetoolpro to install all licenses and activate - Microsoft Office programs all opening and working ok, no banners or issues **if banner occurs in the future i will use KMS_VL_ALL next time to activate** @maxama123 I am still reading through the links you provided, but so far I have ruled out antivirus activity, running OfficeRTool from root, brackets or special characters in folders or username, *5/31/21 Update* Issue with OfficeRTool resolved. Trouble was environmental variables changes I did months ago to work with FFmpeg. I hadn't used OfficeRTool since the original installation before that, so I didnt know it wouldnt work since the env var change. I added the mandatory items back to environmental variables System Path and OfficeRTool works again. Thanks to the MDL Forum and @maxama123 and @Dolmatov for their assistance.
P.S. It may not be necessary but I also unchecked Optional Connected Experiences in Microsoft Options/Privacy just in case.
UPDATE: Just deactivated and reinstalled and reactivated licenses for Office 2019 and still have not gotten rid of the nagware about the license ....sighhhhhh..... My Office 2019 (including Visio Pro and Project Pro) started a few days ago with the Pirated Software/Invalid license stuff. I checked the Optional Connected Experiences and discovered it has been unticked for about forever, so that was one thing that did not work for me. I have been lurking about on different forums to figure out how to get past this. I am about to clear the current licenses and try a relicense to see what happens. maybe will solve it for a while...at least, until the next update