NOTE:

Normally, kernel-mode simulation is NOT needed. In most cases, Magic Camera will choose to use user-mode simulation automatically on 64bit Windows. In such a case, the simulation is transparent to end users. So if you use Magic Camera without any problems on Vista/7 64bit Windows, or if you do not know what is a 'kernel-mode' driver, you do not need to read this article, just go back and use the standard installation pack. Only for some special usage, We supply 64bit kernel mode virtual webcam driver here.

How to install Magic Camera Kernel Mode device driver on Vista/7 64bit Windows?

Magic Camera does support kernel mode simulation of Vista/7 64bit Windows. But due to the restriction of 64 bit Windows, you have to install the driver manually. Please follow the below steps to install Magic Camera on Vista/7 64 Windows:

1) Firstly, install Magic Camera normally. (version 6.8.0 required).

2) Download the driver 'virtual-webcam-64bit-windows-driver.zip' from:
http://www.shiningmorning.com/software/virtual-webcam-64bit-windows-driver.zip

Then extract the zip file to any directory.

3) Run in command mode using administrator privilege:

bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS

Then reboot your PC.

(When reboot your PC, press F8 key upon initial system boot up, and then choose to disable forced driver signing enforcement for that boot session. This step maybe omitted. Read the extended reading section below.)

4) Run command mode using administrator privilege again, then go to the directory that you extracted files in step2.

5) Run command:

devsetup install mcdevice.inf *smmcdevice

Select 'install driver' on the pop up warning dialog.

6) Now you will find our virtual webcam driver is listed on Vista 64bit or Win7 64bit.

7) Then copy the extracted MagicCamera.exe to Magic Camera's installation directory to overwrite the old one. By default, the installation directory is:

C:\Program Files (x86)\ShiningMorning\MagicCamera

This exe patch will enable the kernel mode simulation feature on Windows64 bit.

8) Run Magic Camera, select 'menu->tools->manage virtual webcam device', click 'use kernel mode virtual webcam' box.

9) Done.

9) For your reference. If you want to uninstall the driver later, you can run the command:

devsetup remove *smmcdevice

Extended Reading:
If the virtual webcam driver can not be installed properly, it is most likely the commands on Step3 are failed. To read more information and learn how to fix the problem, please read the following article:

Vista64 simply does not accept any unsigned drivers or processes, causing old drivers or software processes that haven’t been updated cannot be found and installed in Vista x64.

The workaround to run unsigned and uncertified drivers in 64-bit Vista is by using the following command:

bcdedit /set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit -set loadoptions \”DDISABLE_INTEGRITY_CHECK”
bcdedit -set loadoptions \DDISABLE_INTEGRITY_CHECKS”
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
Bcdedit.exe /set nointegritychecks ON

However, when user attempts to run the above command to disable integrity checks on the loading drivers, the following error message appears:

An error occurred while attempting to reference the specified entry.
The system cannot find the file specified.

The problem occurs because Microsoft has decided to disable DDISABLE_INTEGRITY_CHECKS support in updated x64 Vista, which mean users cannot disable the integrity checks anymore. Microsoft is reportedly rolled out the change various updates including KB932596, KB938979, KB938194 and KB941649 hotfixes, and probably Windows Vista Service Pack 1.

The updates also remove the effectiveness of ignoring code signing for drivers in Group Policy. Previously, users can run “gpedit.msc” and navigate to User Configuration -> Administrative Templates -> System -> Driver Installation, and then enable the “Code signing for drivers” and set the option to “Ignore”. This option also no longer works.

There are a few possible resolution or workaround to re-enable the ability to disable integrity checks and have DDISABLE_INTEGRITY_CHECKS option enabled so that it’s possible to load uncertified drivers or executables, such as suggestions below.

1. Uninstall KB932596, KB938979, KB938194 and KB941649 updates from “Installed Updates” in “Programs and Features”, and never install them again. Best still, hide the updates from viewing and accidental install in Windows Update. After uninstalling and rebooting the computer, add the DDISABLE_INTEGRITY_CHECKS option and restart to disable integrity checks again. This method probably won’t work with the release of SP1, which incorporated all these changes.
2. Press F8 key upon initial system boot up, and then choose to disable forced driver signing enforcement for that boot session. However, users have to apply this option every shutdown and restart. An easy solution to the hassle is put computer into sleep or hibernate mode instead of shutting down every time.
3. Use ReadyDriver Plus to permanently disable and turn off disable driver signing enforcement automatically on every system startup.
4. Sign the driver with test certificate, which is supplied with Software Development Kit (SDK) for Windows Vista and .NET Framework 3.0 Runtime Components, and then turn of test signing mode in Vista x64 by suing “bcdedit.exe /set TESTSIGNING ON” command. This trick will need computer running consistently in testing mode, which meant for developers to try out drivers signed with self-signed or test certificate. Risk for running computer in test signing mode is unknown, and there will be “Test Mode” watermarks been labeled on four corner of desktop, although the 64-bit watermark can also be removed.