Note: I have applied KB4465477 (the new servicing stack update) and KB4464330. These updates bump Windows 10 v1809 from v17763.1 to v17763.55. I have applied these patches and while they may have fixed the file deletion bug, they have had no effect on the Edge browser buttons not being skinned by Windowblinds 10.65 in v1809.
I have an Intel I7 in an HP 8300 CMT desktop, an Intel I5 in an HP dv7-4283cl laptop, and Windows 10, 7, and XP Oracle Virtual Machines on the Laptop. If you need specific hardware details, you can look up the HP models I own. My opinion is that the hardware, the drivers, etc., are not the issue. I had Windows 10 v1803 in each of these environments. I converted to v1809 in all environments and the behavior of Windowblinds 10.65 and 10.71 was the same in each environm
Over the last 2 days, I re-installed Windows 10 1803 from the beginning. Pure torture! Re-installed Windowblinds v10.65. I am not seeing any of the issues with skinning associated with Windows 10 v1809. Edge skins O.K. Setting screens don't skin, but the buttons work normally. For that matter, Office apps don't skin, but the buttons work O.K. Technically, Microsoft is encouraging users to roll-back or re-install to v1803 until the issues associated with t
[quote who="glenda stocks" reply="30" id="3675397"] enable titlebar fixes it for me! [/quote] Here's a visual:
...This is not primarily a mouse problem, but a skinning problem. Settings / UWP programs and Edge browsers seem to have no skins... Yes, I'm seeing these same issues. 10.65 seems to fix the problem with the Settings screen, but the Edge browser buttons are still not getting skinned. But then, who uses Edge anyway (...just kidding). I hope these issues can get fixed in the next release soon.
No, Windowblinds is not dead. Keep in mind that there is a license agreement to support the product that you paid for. I think Stardock would let us know if they intended to stop updating and supporting Windowblinds. I suspect that there have been some unforeseen and unexpected issues with the recent release of Windows 10.71 related to the new release of Windows 10 v1809. My opinion is that these issues should have been anticipated better because Redstone5 has been o
I don't perceive this as a mouse problem. If it were a mouse problem, then there would be trouble with clicks, erratic tracking, etc. This is a problem with WB 10.71 and Windows 10 v1809 as I have mentioned in other threads. Going back to WB v10.65 will probably fix these issues.
I have installed v1809 in a VM and on a separate PC. Windowblinds v10.65 works perfectly on both. v10.71 does not. It has the problem with skinning the min, max, and exit buttons on the PC Settings screen as previous mentioned. So v10.65 has been tested and works for me.
Colleagues: If you need to download v10.71, as of yesterday, it could still be found at the following link: https://stardock.cachefly.net/WindowBlinds_10.71_setup_sd.exe However, my personal experience has shown that while it seems stable with Windows 10 v1803 17134.320, as you upgrade to Windows 10 v1809 17763.1 (October 2018 upgrade), it does not seem to properly skin the frames of the PC Set
Keep in mind that as of 9/11/2018 you can update to Windows 10 v1803 build 17134.285. This may not fix the problem with Timeline, but it may not hurt to update from .228 to .285. Using the WSUS Offline Updater is a slick way to update Windows 10. It's a free utility at http://www.wsusoffline.net . Or you can just let Windows 10 chug along and update itself. ~Roger
Stardock Forums
Windowblinds skinning of the taskbar, with Classic Shell installed, has never been an issue in even the latest version of Windows 7. But with the latest version of Classic Shell installed (v4.3.1), Windowblinds has a problem skinning the taskbar with Windows 10 (v1803 Build 17134.228). The workaround for this problem is to uninstall Classic Shell v4.3.1. After the uninstall, Windowblinds immediately skins the taskbar correctly. Then install version 4.3.0 of Cla