I restarted after installing the trail version and installing a theme. My desktop is a black screen. Please help.
Hello,Sorry to hear you are having issues. Try the purge and reinstall steps as mentioned here : https://forums.stardock.com/486023/windowblinds-support-faq#reinstalling . Make sure to reboot after the purge and reboot again after the re-install. Retest and report back.
ThanksBasj,Stardock Community Assistant.
I can’t fucking reinstall a black screen
Try this,
https://forums.stardock.com/486023/windowblinds-support-faq#disablewindowblinds
Thank you,
Basj,Stardock Community Assistant
You legitimately destroyed my pc.
Does your computer startup to the login screen?
If so whilst logging in hold down the CTRL key and keep it held down until your desktop appears. This will prevent WindowBlinds from starting up.
Fixed it. Used a restore point. I realised a combination of things sent windowsblinds into a bit of a fit. Forgot to turn of bitdefender during installation. Messed up another program called classic shell. It seemed to effect the whole system including windowsblinds
Update: restarted and I’m having blue screens. Can’t even repair. I think this software legitimately fucked my pc.
Help.
A BSOD isn't likely to be WindowBlinds at fault I am sorry to say. It will not apply a theme until you have logged in, so if you are having problems prior to the login screen then something else is the problem. WindowBlinds does not replace any system files either.
Are you able to boot into safe mode?
didn’t work. I even tried resetting the os.
I uninstalled classic shell then installed windowsblinds. Could it be that when I restarted things got a bit crazy with them.
I don’t think Classic Shell and WB work together. People here use Start10.
I asked Microsoft support. They say it almost definitely was windowsblinds...
did you guys lie to me
They are almost certainly incorrect.
Correction: I asked on the Microsoft help forum thing. A very experienced dev claimed it is almost definitely Windowsblinds. I cannot see anything else that could do this as it only did this after I installed windowsblinds.
That demonstrates how inept their forum 'help' really is. I'd be more likely to trust the word of the developer of Windowblinds directly...
It is all too common that one of those MS 'forced updates' causes issues that are wrongly attributed to something else that was contemporary. Windowblinds cannot affect your boot/logon as it does not load till after logon...
So how did this only happen after I installed it? I’m not risking destroying my computer again.
Probably because you were rebooting and enabling a Windows Update which caused the issue, and along with whatever other programs you had, specifically 'classic shell' reboot ended at a black screen [first culprit could easily be a driver update thanks to MS Update], then, before seeking any workable assistance you attempted a Windows recovery and as you said got into more trouble.
Put simply, Windowblinds did NOT 'broke my pc'. If you Google 'black screen on reboot' you may actually find your problem.
For future situations... 'Windows Recovery' is a last resort, it is never the first....
I know it can be worrying when a 'black screen' occurs...just the same as a BSOD. Both are curable, provided proper investigation takes place, and not simply some causal coincidence such as installing a program...
What I currrenty am doing. The pc is giving me a blue screen when I start up. I am copying my data onto a hard drive. Resetting is not working. Both types of reset. Gonna reset via USB.
There's pretty much only 2 reasons for a blue screen...bad driver or bad/missing system file.
A BSOD after a system restore is unfortunately not uncommon, though I believe MS is getting better at avoiding them as they are less common these days.
I know one Win 10 update had people getting black screens, but that was quite a while back.
I actually have one Win10 machine that hasn't updated itself in about a year, and everything I do fails to make it happen. It's currently mission-critical, but when it's not I shall deliberately reinstall a newer version over it ...and see if THAT one updates...
I apologise for my dumb anger, it was due to me having open shell installed at the same time which caused the issue. Sorry.
There are many great features available to you once you register, including:
Sign in or Create Account
