Hi, I have an issue with Shadow defender causing extremely slow boot times (3-5m) when C drive is frozen and the Kingston Hyper X Cloud II is plugged in. I'm 100% certain it is the headset and shadow defender. When the headset is unplugged from the USB, the computer boots normally. When the headset is plugged in with shadow mode off, its also fine. The slowdown happens when C: is in shadow mode. My sample size is about 60 computers and it happens pretty much to nearly all of them. I've tried everything from disabling/ delaying the audio device, Changing USB port settings, Disabling other audio devices (m/b) If anyone has any ideas, please throw me some suggestions as this problem has been driving me nuts for most of the day. Thanks.
If it is Shadow Defender that has a conflict with Kingston Hyper X Cloud II it might be the Kingston Hyper X Cloud II software. Some of these softwares want to own the pc at kernel level. I'm not sure if that is the case here but just a thought. I guess that Shadow Defender would not allow anything to completely take over the shadow session. I have read that there have been compatibility problems with most pc (PCs that are not using Shadow Defender) and that Kingston Hyper X Cloud II and firmware etc updates have been released. I don't know much about these headphones but I might look at updating the firmware and exploring that as a way forward. Any conflict with Shadow Defender would be an extremely rare event. There are mixed reviews on these headphones.
Thanks for the reply. I've excluded the entire windows folder and still the same problem. I have tried updating firmware with no success. Any ideas what I can exclude? It slows to a crawl after the first stage of the spinning circles (with the windows blue logo). The spinning circles without the logo and the screen with the username and blureed background take extremely long.
If you are happy with your headphone software. You could try uninstalling Shadow Defender and then rebooting a few times and testing the headphones to your satisfaction. Close down your system Boot Re-install Shadow Defender and see if you get anything different.
Hi, I have tried that. The thing is the Kingston HyperX doesn't install any of its own software, theres no drivers/software which you can download online. I'm pretty sure it uses some windows audio drivers. Under the device manager under audio/kingston hyperx surroun sound, it seems to use all windows drivers and none of its own. I may try individually excluding each of those driver files for now.
@bthology I've had another thought on this. Do you have Fast startup (aka: fast boot, hiberboot, hybrid boot, or hybrid shutdown) enabled in Windows 8/ 10? Tony recommends that it be disabled when using Shadow Defender. Just a thought.
Hi. Fast boot isn't enabled, some of the machines are AMDs which don't even have the fast boot option. I have managed to get time freeze to work on c drive by unticking the "start time freeze with Windows". And putting a batch in the startup folder to freeze after its all booted. Shadow defender has the option to edit shadow mode on shutdown in the Gui and i cannot find any command parameters to add that command to a batch. If I go into shadow mode with the command prompt, i seem to have no option but to enter shadow mode on during boot. Is there a secret command code im missing here?
Thanks for the help So the /now will exit shadow mode after reset? Will try this tomorrow morning Thanks!
I use shadow defender on my second hard drive since time freeze only works on the os drive. But with the knowledge of the /now switch. I can probably remove time freeze Edit : I only put on time freeze as a bandaid fix. But it still exhibits the slow boot problems. So i guess it works almost the same as SD
/now enters shadow mode immediately and the the /exit will exit shadow mode on reboot and put you in normal mode. Read the help.
Thanks everyone for the help. Unfortunately, the problem still persists randomly with the unfreezing on next reboot. I'll have to look for another solution through Windows or with the Kingston headset itself
