Thanks for update, tryied to install Office 2019 Pro, but got offer only for Visio and project 2016, needed to switch to single app to get prompt for 2019 ones
??, no problem here. Just select 5.) for "Office 2019 Professional" to install:: You are talking about Visi 2019/2016 version. Misspelled ? Visio/Project 2019 selection is shown AFTER Visio/Project 2016 selection:
I selected a priorly downloaded "Insider (FAST)" setup package: Using Office Setup Package found in: d:\test\16.0.9031.2004_en-US_x86_Insider_Channel
Is it okay or some bug that in start panel its still under 2016 (word 2016, excel 2016) but when I check about there is 2019 preview
At the moment it's not new Office 2019, but a branded/new labled Office 2016. Microsoft didn't change all locations from 2016 to 2019. We will see the "real" Office 2019 a little later. Now this is only false frontage.
Hi, I have an issue during the start of the installation: "Access denied to installation source Sorry, we ran into a problem accessing a required file. Please check that the installation source has the correct permissions, then try again. Error Code: 30015-39 (5)" - Windows 10 Enterprise 1709 (OS Build 16299.214), fully updated and activated - OfficeRTool 2018/February/12 I removed some stuff using slave77's JATD and I can imagine that a missing Windows component is causing the error. The troubleshooting steps outlined in https://forums.mydigitallife.net/th...wnload-install-activation.62571/#post-1085328 didn't help.
Where are Office setup-files located? If they are on a network share, please copy them to a locally attached drive and try again. Be sure to put them in a subdirectory and not on root (\) of drive and start setup from within. From post #4 - Causes: 3. System file(s) corrupted somehow. Solution: 3. Scan & repair system files integrity: -> run CMD-Shell with admin-rights (rightclick run as administrator) -> enter the following commands one after the other -> sfc /scannow -> dism /online /cleanup-image /scanhealth -> dism /online /cleanup-image /restorehealth You said, you already tried all solutions from post#4 on the first page of this thread. Did you get any errors/reports during sfc and dism /cleanup-image scan/repair? Tweaking Windows is mostly a not so good idea, because gained "benefit" is low and it always will cause troubles in some way or other.
They are on an internal hard drive. I tried to run the setup from two different partitions and also put them inside a subdirectory (e.g. "C:\office") No errors, the tools reported a healthy system and didn't run a repair. I am willing to take that risk in order to keep away the telemetry crap and preinstalled apps. It worked well until now and I wish there was some way to debug this.
You could inspect Office-startup-logfile(s) in %TEMP%-folder. Maybe there are errors listed which help troubleshooting. The files are named %COMPUTERNAME%-%DATE%-%TIME%.log. I suggest to delete all old logs and let Office create new ones.
Do you know if the 'Activation failed' that only happens on Windows 10 insider builds was fixed? Thanks!
Code: "SETUP (0x328) 0x8f4 Click-To-Run General Telemetry" Just a guess: You have stripped of telemetry from Windows, maybe Click2Run-Office relys on some telemetry modules being active/available in Windows? Hence the error.
I'm afraid, it's a Windows Insider problem which can't be solved by OfficeRTool. Only Windows 10 Insider Windows versions sometimes have "specialties" in their license files "tokens.dat" / "cache.dat". These license files were used by Office activation, too. Windows 10 Retail don't suffer from this. It could be, the license files must be deleted/recreated to make Office KMS conversion and activation work again on Windows Insider. Please look in post#5 section (K) Start KMS activation for infos how to do that.
I can confirm that latest tool version still fails to activate on latest Insider build. Just reinstalled Office365 Insider because Windows Search is acting up here as well (doesn't index mail, incorrect permissions on search folder) -> activation failed -> going for tokens now... This Windows Insider build 17093 certainly has some issues, but that's part of the deal. ^^ EDIT: And again, after rebuilding tokens.dat/cache.dat -> no problems at conversion and activation. EDIT 2: Just had a look at Eventlog. At the time activation failed, I get a lot of entries from Security-SPP. ~15 entries are the same: Code: Ausführliches HRESULT. Zurückgegebenes hr=0xC004F022, Ursprüngliches hr=0x80049E00 Detailed HRESULT. Returned hr=..., original hr=... In between there's one other: Code: Vom Regelmodul wurde ein Fehler bei der VL-Aktivierung gemeldet. Ursache: 0xC004E015 AppId = 0ff1ce15-a989-479d-af46-f275c6370663, SkuId = d450596f-894d-49e0-966a-fd39ed4c4c64 Trigger=TimerEvent Error reported by regulatory module during VL-activation. Cause: 0xC004E015 Event-ID was 8233 -> you get some search results on that. That's a reaction to KMS server activation, not conversion itself. Guess we'll have to wait for the next WinInsider build to know if MS changed something on purpose or if it's a bug in the current build.
Can anyone help me with this, please? I posted my issue with Office 2016 a few days ago and not gotten a response yet.