It's working fine for a Beta. Glad to see it's out and looking forward to playing with it.

Quoting Excalpius, reply 20

There seems to no longer be a way to control the transparency of Explorer Window Backgrounds as there was under Windows 7.  Is this feature coming, I hope?

I also can't seem to select OS Default as the default Taskbar/Startmenu in Settings/Use the taskbar and startmenu from... control.  I believe that I was once able to do that.   

Otherwise it works and THANK YOU for returning glass borders, etc. to Windows!!!!  

You were never able to select OS default from default Taskbar / Start menu in settings.

Regarding explorer backgrounds.  Right now that feature is no longer an option on Windows 10 and may have to remain so.  Changes to the OS have caused problems with it.  If we find a solution it would be back but so far no luck.

I can't remove the Windowblinds icon from the system tray. There is no setting for removing it. Never mind, problem corrected itself after second reboot.

Neil, I don't see a button to rebuild the skins list. I can only use the skins that were included in the download.

I copied all my skins into the default folder, as I always have, but no way to see/use them.

WB is only seeing the default skins, Help please.

Tried three downloads/installs, no loading  screen, no skinning. Any suggestions?

Quoting Neil Banfield,

The taskbar must have just been a workaround by selecting a skin that was a ringer.  Or just a side effect of the old setting "I want to use Aero Window Frames but keep the rest of the skin" setting that no longer exists.  

Sorry to hear the Explorer backgrounds thing may be impossible. 

Thanks for the answers to my questions and all the hard work over the years.  

The right-click popup menu on the desktop is unreadable with any blind other than the default W10 theme.  

A reboot cleared up that problem but now I have a runaway DSHost Application.  Shutting it down through task manager has lowered the CPU usage without breaking anything.  

New update:  Killing DSHost has killed the right-=click completely now as well as paused my DeskScapes dream.

What is going on???

Works fine here on all skins.  Odd. 

Tom.. go to sleep!

Menubar button mouseover in Firefox is pink regardless of skin used. Button selected is a darker pink.

When Firefox is skinned with FT Deep Dark by Steva, the resize and close buttons only react if they are clicked on the lowest edge, just one millimeter to click on. But maybe this is on FT Deep Dark. I can live with that for now.

Does SkinStudio 8 work with WB10 beta? or will there soon be a SkinStudio 10 out?

Great to see that the wb10 beta out.

Installed WB 10 beta on Windows 10 64 bit. No skin will apply (apply style to desktop or right click apply style now). I have tried with every skin shown on the Style page. It will change wallpaper though.

DSHost.exe is a key part of Deskscapes.  Killing it would break things such as pausing DS and possibly stopping right click working.

If that process is using lots of cpu it is because you are using a video dream that needs lots of cpu to decode.

Installed WB10 and for awhile it worked just fine. I was able to change skins without a problem. Then when I scrolled down to Naked Noir skin WB10 stopped working. This happened three times. I'm trying to upload a screenshot but photobucket is being a pain in the rear. But that's not all. Chrome was not skinned completely, no max, min or close buttons and the UI had no borders and no buttons. I had to use task manager to close it. I had updated certain drivers and that was part of the problem. Did a system restore and that brought some of it back. Don't have WB installed ATM, trying to figure out what's going on but WB10 does not seem to be working correctly on 8.1. The upload to photobucket failed so I have no screenshot. Going to reinstall WB8.13.  

If you had just switched from Aero to a WB skin with Chrome open it may have no frames until you close ALL instances of Chrome and reopen them.  This is a side effect of their sandboxing technique.  This is true with WB8 as well.

I'd love to know the answer to that question too. 

Never had that problen with WB8. Even with Chrome open changing skins was flawless. I did it just now changing from the default skin to ProjectZ with my browser open.

BTW: Haven't given up on WB10. Going to redowload it (system restore deleted the installer package) and give it another shot. Got to play.

The problem only happens if the very first skin Chrome had when it started was Default.

I am having the same problem. same OS.

 I tried 3 separate downloads/installs, I get a wait screen on first attempt to apply but nothing gets skinned. Further attempts and nothing at all happens. Any suggestions on this?

Did you have WB8 installed before?

 I do have Start 10 installed.

Just tried another install after completely removing all WB entries in the registry, still no go.

I found that when installed on win10 64bit, Rainmeter needed an exception to not skin it.  All Box Sync fails to start.  That also need an exception.

Yes, upgrade to Win 10 from Win 7. Would WB8 carry over into Win 10? 

Just confirming Chrome here has an unskinned window titlebar (i.e. it's transparent), so no min/max/close buttons either. The other three sides of the window frame are there... That's after a reboot. I'll check after a shutdown.

Also applying a skin seems to need you to double-click on the WBA file to 'install' it - I can't seem to find a way to just refresh the skin list to find skin folders I've copied in. (maybe that's not an option now?)

But what a relief to have WB on my PC again. Vanilla Windows 10 looks so shit - what were they thinking?...

Thank you.

(Windows 10 64-bit)