I’m not sure that Stardock has dumped the skinning of all browsers because I’m seeing that the Internet Explorer titlebar is still getting skinned by Windowblinds. Instead, it appears to be “cherry picking” which apps get skinned and which apps are abandoned. While Stardock is able to do this, the consumer is also able to seek skinning solutions elsewhere. I consider this to be a lose-lose scenario for both Stardock and the consumer. It seems like a better solution cou
r_pinkard
After converting to WB v10.83, the Firefox titlebar is no longer painted with the appropriate color and the buttons are default buttons for Windows. The Firefox titlebar is always white. The buttons are always the style for Windows 10. WB will not paint or alter the buttons. Firefox v70.0.1 Windows v1909 (18363.476) Currently reverting to v10.82 which correctly paints the Firefox Titlebar. In the example below, the Firefox titlebar is white with Windo
[quote who="Urban1" reply="179" id="3734263"] excuse me for a stupid question but how do i make it look dark? [/quote] I don't think your question is stupid. There are actually several Windowblinds skins that you can use to achieve a dark mode effect without changing Windows settings. In fact, one of them is called "Dark Mode", it does a good job, and appears to currently be one of the most popular skins on wincustomize.com Dark Mode by Vad_M <a href
While I will admit to a degree of levity in my commending stardock developers, I still think that they deserve recognition for all the betas they have recently released. This demonstrates an unusual level of responsiveness. I apologize if my posting of an animated rose offended anyone. Just thought it might arouse a laugh or two. I have used Windowblinds on and off for several years. I don't think that it is realistic to believe that Windowsblinds is going to s
[quote who="ALMonty" reply="166" id="3733859"] Quoting r_pinkard, reply 163 Quoting BigDogBigFeet, reply 160 For the lif
[quote who="BigDogBigFeet" reply="160" id="3733817"] For the life of me I cannot figure out why I am 2 versions behind everyone on WIN 10. It still shows updates are current. Any ides on how to tell it to update? [/quote] Firstly, your build is Redstone 4 (17734) which
[quote who="ELFswe" reply="32" id="3733435"] Something just changed with the latest automatic update (10.65?). The black bar that have been covering the minimize, maximize and close button is gone. Any application with it's own skin seems to cause issues. Steam has extra buttons. Radeon Settings has extra buttons and bars around it and it's whole UI is also shifted a couple of pixels (the clickable areas don't correspond to the UI). [/quote] Are
[quote who="sdRohan" reply="145" id="3733073"] Quoting r_pinkard, reply 144 I'm getting the same discrepancy with Windowblinds v10.74 showing Windows Enterprise and WinVer showing Windows 10 Pro. It's likely a registry read (that's what it says) - it has no bearing on any issues. <b
I'm getting the same discrepancy with Windowblinds v10.74 showing Windows Enterprise and WinVer showing Windows 10 Pro.
So you've run sfc /scannow, Windows appears OK, the video driver worked before the 17763.134 update, the Stardock service is running, you are running the latest beta of WB, and it's still not working. I would be curious to know if you could revert back to the version of Windows 10 prior to updating to 17763.134. You could try reverting to a system restore point prior to the update. But the problem with system restore points is that they don't always work! Sometimes you
[quote who="masterbas" reply="136" id="3732996"] Did all the things you pointed out with a negitive out come on a working windowblinds I don't know why you stated it as a Opinion but it are facts and like logic to check out to make sure to get to the core of the problem. It started after updating to 17763.134 with the beta that is all I know so figure it out [/quote] You are saying it is an update to 17763.134. Update from what? Update from v1803, update from v18
[quote who="sdRohan" reply="133" id="3732957"] Quoting masterbas, reply 121 Maybe it is because i'm on LTSC enterprise version dunno We have no experience with the version (what it may lack or restrict) but I am curious if you, yourself, chose to use that version or if it is a corporate decisi
[quote who="masterbas" reply="117" id="3732796"] btw windows updated to 17763.134 and now windowblinds stopped working just saying [/quote] I have updated 17763.1 several times from .1 to .17, .55, .104, .107 and now to 17763.134. Sometimes, the Stardock Service does not initialize properly after an update. Make sure the service is running and set it to automatically start. Press the Windows+R keys, and in the run box enter services.msc. Go down to t
[quote who="dkasper9e93" reply="5" id="3732677"] Hello ALMonty Thank you for responding, but you are using a different skin than what I am using. I choose Lantana as I read in the forums to choose a default skin that come installed with WB before posting so it would be easier to re-create / look into. Hello Basj, Thank you for responding as well. I see it skinned correctly on your screen shot, the Windows Defender. Going with just the defaults, for some r
[quote who="ALMonty" reply="110" id="3732367"] Speaking of Win 10 Pro. This morning I received a message the my OS is not activated. What happened was I had a dual boot with Win 8 and I deleted that partition so I could just have 10. 10 was activated because of 8, now that its deleted 10 doesn't see an activation. I tried to use the 8 pro key that doesn't work. 2 things I can do, install 8 again then upgrade to 10 or buy a key for 10. Either way I have to start all over again.
[quote who="Uvah" reply="99" id="3732302"] What is the difference between version 1809 and 1804 which is the one I have. [/quote] The answer to your question is five months. Windows 10 is a series of Windows builds separated by 5-6 months. Typically, each build has features that have been removed, replaced, added, etc.&nbs
[quote who="Jafo" reply="97" id="3732265"] Quoting r_pinkard, reply 95 I used to work for MS and the saying was: "Beta Means Broken!" So this is no beta. You must have worked for them prior to Windows 10, as now there is technically no such thing as a non-beta OS. Microsoft decided in th
OK. Let's try this again. Here's the latest official release of Windows 10 v1809 17763.107. This is not an insider release (i.e. 18XXX.XXX) or some other beta in disguise. I used to work for MS and the saying was: "Beta Means Broken!" So this is no beta.
Somehow, I answered Elektro Studios post in the wrong thread! I'm wondering how that was even possible? So I'm re-posting here in the right thread. [quote who="ElektroStudios" reply="18" id="3730733"] Hey guys, these days since the first comment of @r_pinkard I'm wringing my head to try to find out how can I manage to have an ISO of the Windows 10 v17763.55 (or higher version, if we are talking about a higher stable one). The thing is that I need it in I
The 10.73 beta is working great with 17763.104. No complaints here.
I'll be Captain Obvious here. Captain Obvious says: "Don't install and run insider builds because they are betas. And......wait for it...BETA MEANS BROKEN!" The lastest real build is Windows 10 v1809 17763.104
Insider releases are alphas and betas. Sometimes beta means broken. I am currently running Windows 10 v1809 17763.104. The Windowblinds v10.73 beta is working great with it. Even the apps are skinning now. I can't really complain, because I've imported a lot of Windows XP msstyles into Windowblinds format and it's probably a bit unfair to expect these imports to skin all the stuff in Windowblinds 10. But a lot of styles simply vanished from the XP era. 
I'm currently using v17763.55 as a host for 3 Oracle Virtualbox VMs: XP, Windows 7, and Windows 10. Windowblinds 10.65 works fine if you ignore a few things about it. The problem is that it doesn't skin Apps correctly. The min, max and exit buttons are all goofed up. Windowblinds skins "program interfaces" great, but not the apps (including Edge). But then, I don't use apps. I don't believe apps belong in Windows anyway, they are OK on phones, but not in Wi
If you use the media creation tool to download an ISO of Window 10, you will probably get version 17763.1. Some Microsoft servers are still distributing this version as an ISO. 17763.1 has issues and will delete files, user profiles, and sound drivers on some computers. It depends on the type of Windows you are running before you install the upgrade. To the best of my knowledge you cannot download any other version of Windows 10 v1809 17763.1 in ISO form at this time. <
Microsoft Windows 10 v1809 17763.1 is not a stable release. To determine your version of Windows 10, press the Windows Key + R, and enter "winver" and click OK. If you are currently running version 17763.1, you may wish to update to version 17763.55 for stability. To update your version of Windows 10 1809, download and manually update with KB4465477 first, then download and manually update with KB4464330 second. To manually update, simply double click on the .msu f