![\"Runtime](\"https:\/\/i0.wp.com\/pbs.twimg.com\/media\/B0JMbQpCEAAFFM5.png?resize=296%2C155&ssl=1\")
<\/p>\nI think I’ve logged more IT support calls this week than ever before… most of which have resulted in frustration (possibly on both ends of the phone) – I guess that’s the danger of being a technical end user, who doesn’t really want to have a 90-mile round trip for a desktop support technician to look at a problem when I can really fix things for myself.<\/p>\n
Yesterday’s call was really just a “niggle” though – but, as I was in the process of fixing some of the issues on my PC, one I wanted to be rid of…<\/p>\n
Every time I booted the PC (not resumed from hibernation – just on a cold start or warm reboot), I was presented with a Visual C++ Runtime Library error:<\/p>\n
<\/p>\n
It wasn’t a major issue – more of an annoyance – but Googling didn’t turn up much\u00a0so, once again, I tried the IT support route. When it didn’t look like I was getting very far, I also tweeted ByCrypt – who were very helpful but, in the meantime, the correct support channels came back with the solution (and a 100% success rate, I’m told).<\/p>\n
The issue was that a previous software update had left two startup entries for the BeCrypt system tray\u00a0application active – one 32-bit and one 64-bit:<\/p>\n
![\"\"](\"https:\/\/i0.wp.com\/www.markwilson.co.uk\/blog\/images\/becrypt-msconfig-entries.png?resize=365%2C84&ssl=1\")
<\/p>\n
Disabling the 32-bit\u00a0C:\\Program Files (x86)\\Common Files\\BeCrypt\\BCSystray.exe entry (not the 64-bit\u00a0C:\\Program Files\\Common Files\\Becrypt\\BCSystray.exe version) and restarting the computer cured the problem.<\/p>\n
<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"