Thanks however Sets caused more issues for some of my apps I use on a regular basis. Its was still alpha/quarter baked imho. I will let m$ get it a tad more stable first. ~MC
I'm using Windows for Workstations and found this behavior beginning with the 1803 builds. My solution in Windows Security/Device Security/Core Isolation. I believe the default of this changed from off to on with the 1803 builds. Turning this off restored the normal operation of right-clicking. Bear in mind it does reduce security.
With this new build (17704) my Hyper-V wont start because of what it says in attached. I jumped through many hoops, still no Joy. I also managed to break my network/internet connection on Host (b17704) I noticed earlier that moving documents between this PC & another was very slow I checked the other W10 on this PC & it's network/internet worked fine. So I tried a 'Network Reset' (attached) that worked great incl. copying documents between PC's is fast again. Spoiler *Edit: I fixed the Hyper-V problem, life is good again
Glorious white title bars.. how about you start with addressing that for example, with: Code: Windows Registry Editor Version 5.00 [HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\DWM] "Composition"=dword:00000001 "ColorizationColor"=dword:ff000000 "ColorizationColorBalance"=dword:00000064 "ColorizationAfterglow"=dword:d9000000 "ColorizationAfterglowBalance"=dword:0000000a "ColorizationBlurBalance"=dword:fffffff6 "ColorizationGlassAttribute"=dword:00000000 "EnableWindowColorization"=dword:00000000 "ColorPrevalence"=dword:00000001 "AccentColor"=dword:ff36383c;aa bb gg rr "AccentColorInactive"=dword:ff4a4c50;aa bb gg rr [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Themes] "ColorSetFromTheme"=dword:00000001 [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Themes\Personalize] "ColorPrevalence"=dword:00000001 "EnableTransparency"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\FlightedFeatures] "ImmersiveContextMenu"=dword:00000001 [HKEY_CURRENT_USER\Control Panel\Desktop\WindowMetrics] "BorderWidth"="0" "PaddedBorderWidth"="0" Edit: actually, that will only mask it a little. Forget about the no border that came with Sets, now it's reverted to older non-removable border (like in rtm)
It's something, but yeah something that can't be completely solved for now that Sets is crippled. I'm fine with the white titlebars and borders, it fits in the applications where everything else is white. It just is an eyesore in Explorer where the rest of the application is dark. Hopefully Sets makes it back soon, but given how it won't make it to RS5 we won't get it back until RS6 hits Skip Ahead which won't be until late August or early September if following when RS4 first hit Skip Ahead. In other news I just had my computer Green Screen on me while it was idling. Ended up being a page fault in nonpaged area and the responsible module was Ntfs.sys. Not too happy about that. I'm not sure if it is the driver for the build being bugged. It could be because Windows decided that having the WinRE on my hard drive was unacceptable and it took a bite out of my SSD to shove the new WinRE in. I don't have any answers yet, I really don't feel like analyzing the memory dump and the event viewer is of course unhelpful. If it happens again I guess I'll end up getting my Sets back by going back to 17692.
Sorry, all I saw was that the thread title was "Windows 10 Insider Preview Build 17704.1000 (PC) [FAST - RS_Prerelease]" and I'm using Windows 10 Insider Preview Build 17704.1000 (PC) [FAST - RS_Prerelease] version 1803 Maybe it should be retitled to version "1809 only" ??
Anyone else having issues after unlocking from lockscreen where taskbar/systray/explorer.exe gets all wigged out and explorer.exe needs to be restarted? Also after idle (on lock screen) for a while and I unlock and get to desktop I get no activity (cant ping anything at all gateway or myself) if I disable my Ethernet NIC and re enable it it work. I did an upgrade from previous insider build (trying to avoid a fresh reload). Im having way more issues with this build than I had with previous builds. ~MC