I do not envy the VirtualBox developers who have to cope with the Microsoft certification issues when supporting obsolete Windows versions today. In the case of Windows XP, all affected users reported 0圎0000304 so far, which can be translated to "ERROR_INVALID_CATALOG_DATA: Catalog referenced in the INF is invalid or could not be found", which hints to a combination of (3) and (4). attestation signing), with potential mistakes in the attempt to attach 3 signatures while CAT files probably only allow 2.įor Windows 8.1, Windows 7 and Windows XP, the affected users get different error codes returned by VBoxDrvInst.exe. (4) new certificates used to sign some of the current GA files with new signature methods (e.g. (3) accumulated INF, CAT and driver files being out-of-sync between the two installation directories C:\Windows\System32 and C:\Program Files\Oracle\VirtualBox Guest Additions, which I discovered lately, (2) trusting Oracle software (singly or permanently) by the user during installation, which also combines with (1), (1) accumulated higher level certificates in the different Windows certificate stores (there is more than one accepted certificate chain), Some of the interrelated mechanisms involved are Then, hit the folder with the green arrow. Under Hard disk, select Use an existing virtual hard disk file. The exact circumstances are not known (to me), but the order of all Windows XP updates and VirtualBox GA updates could play a role. Finally, you need to assign the virtual hard disk we extracted from the Windows XP Mode executable earlier. Mpack wrote:But if the problem is caused by new certificate types then why would the age of my XP install matter?
0 Comments
Leave a Reply. |