When you preview a dream within DeskScapes, the dream file (.dream) is extracted to (and remains on) a directory on the C drive. That's where the dream is read from when you run it. So it really doesn't matter where you store the .dream files, other than space usage and perhaps the initial extraction, you're running the dreams from the C drive. You do need to leave the .dream files saved in the directory that you've chosen though, because that's where Deskscapes looks to k
DaveRI
One other thing occurs to me- I think the Win10 keys are linked to your Microsoft account. If you haven't already, you might try logging into your account while on the machine. There's a section in your user profile for managing devices, you might look at that. There's also a Win10 option to log in with your Microsoft account. I have that turned off (and I'd guess you do too), but you might need to have that turned on to get the activation to work (?). <
[quote]but I can't find a way to call MS like we used to be able to with licensing issues. I need to speak with somebody at MS to find out what is going on with my copy of Windows and product key. Anyhow, if anyone has any ideas as to how best to proceed, please let me know [/quote] Man, their support section is such a rabbit hole. I found this - you can run an already-installed Activation Troubleshooter that might help, see the section about a third
And I should give you a little heads-up about tweaking the shipped skins in case you don't already know. You want to either keep the edited versions backed up or use Skinstudio to copy them to a new skin, the WindowBlinds updates tend to mess with them, especially if you do an uninstall before installing the newer version of WB.
This one has a separate substyle with a smaller start button for small icons. It's a Win7 skin, probably could use a little minor tweaking for Win10 but it should look ok: https://www.wincustomize.com/explore/windowblinds/8279/
[quote who="WebGizmos" reply="19" id="3724033"] So...what would be blocking it? [/quote] Shot in the dark- you might try temporarily disabling antivirus, any other anti-malware, as well as firewall. Purely guessing.
Forum seems to be tacking "...wincustomize..." to the beginning of the link. Try this: https://www.ghacks.net/2018/08/20/how-to-enable-windows-defenders-potentially-unwanted-programs-protection/?_m=3n%2e0038%2e2196%2ehj0ao01hy5%2e2agp
[quote who="pawztoo" reply="19" id="3723655"] I think I will have to put the system on again. [/quote] I wouldn't jump to that just yet, you may very well end up at the same place. Give support a day or 2 to look at it.
(If I understand him correctly, he's running WB10 on Win7.)
Guess it might help if I did this: Windows 10 Home (17134.rs4_release.180410-1804) WindowBlinds 10.7 BETA (050 - Windows 10 Edition) - 64 bit OS Window titlebar blur features are enabled on this operating system Wblind.dll 2018/07/08 11:45:50 Wblind64.dll 2018/07/08 11:45:29 Wbsrv.dll 2017/03/28 08:53:46 WB10Config.exe 2018/07/07 17:31:18 Wbload.dll 2018/07/09 10:52:37 Screen10.exe 2017/03/28 08:53:17
I don't use Edge but I've been sitting here putzing with it. Just to add to the confusion, it seems to me that I have a lot more luck dragging the window by clicking/dragging at the right side of the titlebar, like just a little to the left of the window buttons. It seems to work consistently that way. Might depend on where you're clicking when you're trying to drag it.
[quote who="MagikGimp" reply="103" id="3722267"] Chrome runs fine but yes, the title bar doesn't skin properly [/quote] Not sure you were looking for help with that, but anyway replies 4 or 6 here should take care of it: https://forums.wincustomize.com/489575/page/1/#3717744
[quote who="JcRabbit" reply="6" id="3721645"] the next release is going to be HUGE: it adds support for multiple tabbed docks, vertical tabbed docks, tabbed dock scaling (you can now make them bigger if you have poor eyesight or a huge screen res) and something new called 'Drawers' (a mix between a single-tab tabbed dock and a dock). [/quote] [e digicons]:thumbsup:[/e] That does sound, well, HUGE [e digicons]:)[/e]
It kind of smells like borked up file permissions to me. Ross, right-click on one of the actual extracted icon files that isn't loading in your Icon Packager Themes directory and make sure security permissions for "Users" is set to at least "Read & execute" and "Read".
See reply #3 here: https://forums.wincustomize.com/488650/page/1/#3719682
[quote who="Uvah" reply="18" id="3720375"] So I am my own organization, number of employees...9. Me and my felines who think they're monkeys. [/quote] If I know cats, the cats would be The Organization and you would be ... the butler.[e digicons];)[/e]
You can try this if you like. I run on a Standard (Non-Admin) login in Win10. I have to apply the icon packages twice: 1st time, launch Icon Packager using the right-click "Run as administrator" option. Apply the icon package I'm wanting to apply. (This will also change the icons on the administrator login, in case it matters.) 2nd time, launch Icon Packager normally and apply the same icon package.
Purring right along here (as far as I know). [They could uninstall IE and Edge and I might notice it after a couple of years. [e digicons];)[/e] ]
I didn't hate Win98, but I got more than my fill of it. It did used to let you change various colors to some extent and save them as themes which was helpful. Win98 was what I was on when I first discovered WB. XP itself would also let you apply a "Classic" look which I think was a Win98 look, and let you change the colors to some extent, and save them as themes. I mixed up about a half-dozen combinations and used to load them up occasionally for a change of pace.</p
There is a useful link at the bottom of this page, "Compatibility Matrix" underneath System Requirements, which spells out what works with which versions of Windows: https://www.stardock.com/products/odnt/
See if replies 4 or 6 here straighten it out: https://forums.wincustomize.com/489575/page/1/#3717744
By the way, you mentioned ClassicShell in your other thread. There does appear to be a conflict between ClassicShell and WindowBlinds. I don't believe anything as severe as what you were experiencing, usually taskbar issues I think, but you don't want to have both installed at the same time in case it crosses your mind again. https://forums.wincustomize.com/search;classicshell
[quote]So is there a way to disable windowblinds upon boot if I bypass the login screen? [/quote] You can apply the "Default theme" (1st theme) in WindowBlinds, then it will stop loading at boot but you'll be using the standard Windows theme. Otherwise, none that I'm aware of. Since you're very much wanting to use WindowBlinds though, I'd be inclined to let it load at least for awhile until I felt like whatever issue was resolved.
I'm not offering this as a "fix" but merely as a tool that might be helpful while you're struggling with this: To completely prevent WindowBlinds from loading at boot, hold down the [Ctrl] key while you're pressing [Enter] to log in at the login screen.
Back up your skin first. I'm not joking, I haven't played on Win7. &n