I've tried to install virtualbox - 5.2.8. (installing with "run as admin" enabled) and when I come to the end of installation it rolls back and a window opens saying Fatal error during installation and no reason is given.
I enabled MSI logging and here is this file,
thank you.
I am running windows 10.
Fatal error during installation -- Log error included --
Executing the TextStyle view failed
I keep running into these errors while installing and was wondering if anyone has a solution.
I believe it is these lines which indicate the error in the MSI log.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2888. The arguments are: TextStyle, ,
Action ended 12:41:43: VBoxFatalErrorDlg. Return value 2.
Action ended 12:41:43: INSTALL. Return value 3
CustomAction MsiInstallDrivers returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (A8:38) [12:41:40:264]: Closing MSIHANDLE (107) of type 790536 for thread 10448
Action ended 12:41:40: InstallFinalize. Return value 3.
The full log is available in my other post.
Thanks
I believe it is these lines which indicate the error in the MSI log.
The installer has encountered an unexpected error installing this package. This may indicate a problem with this package. The error code is 2888. The arguments are: TextStyle, ,
Action ended 12:41:43: VBoxFatalErrorDlg. Return value 2.
Action ended 12:41:43: INSTALL. Return value 3
CustomAction MsiInstallDrivers returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox)
MSI (s) (A8:38) [12:41:40:264]: Closing MSIHANDLE (107) of type 790536 for thread 10448
Action ended 12:41:40: InstallFinalize. Return value 3.
The full log is available in my other post.
Thanks
-
- Site Moderator
- Posts: 39134
- Joined: 4. Sep 2008, 17:09
- Primary OS: MS Windows 10
- VBox Version: PUEL
- Guest OSses: Mostly XP
Re: Executing the TextStyle view failed
Have you tried downloading VirtualBox again? And doing a checksum test on the download? I have to say however that this looks like an MSI/registry problem to me - if the problem was systemic to the installer then lots of people would be getting it.
p.s. Cross posting is against the forum rules, so I have merged your two topics.
p.s. Cross posting is against the forum rules, so I have merged your two topics.