I think these are the .log files refering to the Office 2019 C2R failed installation (I've uploaded a zip file with them). The installation seems to do everything fine until the end, where some task fails and ends the install. I can't decypher what actually happened, so maybe you'll be more lucky @abbodi1406
Yes, I used an ISO I made with all updates and also installed the latest monthly rollup and .NET Framework 4.7.2. Office 2019 on Windows 8.1 installed just fine with less updates.
Office cannot install SPPRedist.msi (the osppsvc.exe and licensing) the cause is not very clear, just Exception check logs in Event Viewer do you have any KMS solution installed?
Sorry, debugging is not my field all i could understand from logs is that integrator.exe crash and not compatible with kernel32.dll try to install VC++ 2017 redist (both x64 and x86) maybe that helps
@ratzlefatz did you use a VM? Just curious, because this error I'm getting is really weird. I'll be doing some further testing to try and pinpoint the issue either way.
Yes, it's running on a VMware Player 14.1.3 build 9474260 virtual machine. All Win7 updates included. All Visual-C runtimes included (used VS-runtimes AIO.setup from abbodi1406).
It means MS haven't tested office 2019 compatibility issues on older windows releases and although it may seem to install fine, but since MS isn't addressing any issues with older releases then it may not be the best decision to use office 2019 on older windows.
OK guys (and explicitly myself, too). Everyone's position was made up. Don't raise a philosophic discussion. Let's come back to digital Office2019 topics please.
In first post, suggestion to use kmspico and mtk should be removed because they can't activate office 2019.