Another program rendered incompatible with Windows 10’s fall Creators update

It’s fast becoming apparent that Windows 10’s fall Creators update is a lemon, just like the original Windows 10.
   As those of you who have followed my posts know, my PC began BSODing multiple times daily, on average. There were brief interludes (it went for three days without a BSOD once, and yesterday it only BSODed once) but these (now) anomalies don’t really diminish my ‘three to six per day’ claim I made earlier by much.
   And it’s all to do with drivers. I won’t repeat earlier posts but the result was that drivers that came with Mozy, McAfee, Malwarebytes and Oracle Virtualbox caused these. In Mozy’s case, it was an old one. Same with McAfee, the remnants of a program that even their removal tool could not take out. Malwarebytes didn’t even show up in the installed programs’ list, and required another program. In Virtualbox’s case, there were both old and new drivers. They all had to be removed, in most cases manually, because removal procedures don’t seem to take them out. This is a failing, I believe.
   But with all these drivers gone, I still had a BSOD this morning. Four before lunch. The culprit this time was a CLVirtualDrive.sys driver that came with Cyberlink Power2Go, which came bundled when I replaced by DVD burner last year.
   And Cyberlink knows something is wrong with this driver. On December 13, two days after I began getting BSODs, it issued a patch for its latest version. Of course, it leaves those of us with older versions in the lurch, and I was surprised to find that the one it had issued for mine (years old) wouldn’t even run because I was on a bundled OEM edition.
   I’m crying foul. If your program is causing BSODs, then I feel it’s your responsibility to help us out. It shouldn’t matter if it’s a trial version, because this is a window into your business. This signals that Cyberlink doesn’t really want to offer a simple download to prevent users from losing hours each day to fixing their computers, even when they’re partly to blame for the problems.
   Let me say this publicly now: if any of our fonts cause system crashes like this, contact me and I will provide you with fresh copies with which you can upgrade your computer.
   I’m removing Power2Go as I write. It’s superfluous anyway: I only use it because it came as part of the bundle. Windows’ default burning works well enough for me.
   But there’s one thing that Cyberlink’s pages have confirmed: the fall Creators update has problems and it seems to me that it is incompatible with many earlier Windows drivers. We can lay a lot of these problems at Microsoft’s feet. Indeed, based on my experience, you could go far as to say that Windows 10 is now incompatible with many Windows programs.
   That’s all well and good if you have a new computer and the latest software, but what of those of us with older ones who will, invariably, have older drivers or upgraded from older systems?
   Are we now reaching an era where computing is divided between the haves and have-nots? It’s not as though decent new computers at the shops have got any cheaper of late.

Next part: click here.


You may also like




2 thoughts on “Another program rendered incompatible with Windows 10’s fall Creators update

Leave a Reply

Your email address will not be published. Required fields are marked *