Changes between Version 64 and Version 65 of Windows build instructions
- Timestamp:
- Jun 20, 2017 9:20:35 AM (7 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Windows build instructions
v64 v65 163 163 Don't build + package the webservices API server. 164 164 VBOX_WITHOUT_HARDENING=1:: 165 Disable Windows hardening. Useful for testing. Do '''not''' use this setting for production builds! Without hardening the binaries are not signed and !VirtualBox.exe can be started straight away from the out\...\bin directory (`kmk packing` + installation not required). 166 167 === Only for 64 bit builds: setting up self signing === 165 Disable Windows hardening. Useful for testing. Do '''not''' use this setting for production builds! Without hardening the binaries are not signed and !VirtualBox.exe can be started straight away from the out\...\bin directory (`kmk packing` + installation not required).[[BR]] 166 Please note that it's still necessary to enablg [#CodeSigning code signing] to be able to start VMs as Windows refuses to load unsigned kernel drivers. 167 168 === Only for 64 bit builds: setting up self signing === #CodeSigning 168 169 169 170 Setting up test signing will allow to build signed binaries to make Windows happy. To use the test-signed binaries, the target machine has to run in test signing mode and the test certificate has to be installed on the target machine. … … 222 223 223 224 Build stops immediately with ''!***You need to enable code signing for a hardened windows build to work''.:: 224 The message is clear: Code signing must work as Windows will only work with properly signed drivers. A temporary workaround for testing is to add '''`VBOX_WITHOUT_HARDENING=1`''' to your `LocalConfig.kmk`. Never use this setting for production environments!225 The message is clear: Code signing must work as Windows will only work with properly signed drivers. If [#CodeSigning code signing] is not properly set up then a temporary workaround for testing is to add '''`VBOX_WITHOUT_HARDENING=1`''' to your `LocalConfig.kmk`. Never use this setting for production environments! Enabling code signing is still required to start VMs, see [#CodeSigning above]. 225 226 226 227 Typing `kmk` raises a message box ''The application was unable to start correctly (0xc0000022). Click OK to close the application.''::
