Neil is serious: REBOOT after the uninstall.
I was already at 10.0.7 via WB update several weeks ago before the windows update I finally installed this AM & I still ran into this issue.
and since I always run into issues with WB and windows updates, I usually have a good strategy for this (see below)...
I verified a successful windows update install by logging into my 'minimal mod' admin account and then found this issue when I logged into my 'all mods active' admin account to check for such conflicts...
So, I want to emphasize for anyone stumbling upon this thread & still having this issue...really do follow Neil's procedure:
"To those with black screens: PLEASE UNINSTALL WB, REBOOT and then reinstall WB 10.0.7. It will work fine."
Also, since this black screen issues happens frequently for users like me, I encourage anyone who uses WB and has encountered this issue on their machines to create a local windows admin account that does not have WB or Fences, or windowFX loaded/active...and do windows updates from there...
I started doing this since I first ran into this trouble back with WB in one win 8 update several years ago...that way at least windows updates go fine and you can always access your local no/minimal mod admin account to sign into and problems only show up when you are ready to look for them by logging into the 2nd admin account that has mods like WB active.
Also when troubleshooting issues like this, one can also just disable the respective Stardock service process rather than uninstalling the whole Stardock program...I do this to verify if the conflict is just with WB...
(for example, in this case, I confirmed that simply setting my Stardock WB service to start manually enabled me to login just fine to even my 'mods active' admin account check WB configs etc...and as soon as I manually started the WB process I could watch WB apply the style to several windows before devolving to the black screen...interestingly the bitdefender widget & WB config window remained functional but I still had to do a hard shutdown since ctrl-alt-del still gave only an error msg...)
to Neil: Thanks again for your help! 