Closest I got with AutoHotkey was this: Code: #NoTrayIcon #Persistent #SingleInstance force #NoEnv ; Recommended for performance and compatibility with future AutoHotkey releases. ; #Warn ; Enable warnings to assist with detecting common errors. SendMode Input ; Recommended for new scripts due to its superior speed and reliability. SetWorkingDir %A_ScriptDir% ; Ensures a consistent starting directory. ; registry reading and writing from tomte: h*tp://autohotkey.com/board/topic/36290-regread64-and-regwrite64-no-redirect-to-wow6432node/ SetupWatch(byRef hEvent, byRef hKey) { ret := DllCall("Advapi32.dll\RegOpenKeyExW", "uint", 0x80000001, "str", "SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Accent", "uint", 0, "uint", 0x0010 + 0x0001 + 0x0100 + 0x20006, "uint*", hKey) if (ret != 0) ExitApp hEvent := DllCall("CreateEvent", "uint", 0, "int", true, "int", false, "uint", 0) if (!hEvent) ExitApp } main() { OnExit, cleanup SetupWatch(hEvent, hKey) Loop { ret := DllCall("Advapi32.dll\RegNotifyChangeKeyValue", "uint", hKey, "uint", true, "int", 0x00000004, "uint", hEvent, "int", true) if (ret != 0) ExitApp ret := DllCall("WaitForSingleObject", "uint", hEvent, "uint", 0xFFFFFFFF) if (ret = -1) ExitApp IfWinExist Color and Appearance WinWaitClose sValue := 0xff520018 DllCall("Advapi32.dll\RegSetValueExW", "uint", hKey, "str", "StartColorMenu", "uint", 0, "uint", 4, "uint*", sValue, "uint", 4) PostMessage, 0x031A, 42,,, ahk_id 0xFFFF ;ahk_class ExploreWClass } ExitApp cleanup: if (hEvent) { DllCall("CloseHandle", "uint", hEvent) hEvent = 0 } if (hKey) { DllCall("Advapi32.dll\RegCloseKey", "uint", hKey) hKey = 0 } ExitApp return } main() This would retain the border and taskbar colour but would set the Start Menu colour to sValue. A lot needs fixing, though, and that's assuming that there's not a simpler way of doing it.
Need help in installing Win 10.. My config: Win 8.1 x64 Legacy BIOS with MBR partition scheme, OPROM Enabled in Bios Settings. Gets stuck at Windows Logo without cursor while trying to boot/install from flashable usb drive
I haven't checked out the Windows 10 TP ISO, nor do I plan to . First version I'd go to is the RC most likely, or at least a proper CP. If the installation is anything like Windows 8/8.1, setting it up on a modern computer with UEFI is pretty easy. You just format a flash drive with FAT32, open the ISO in Explorer, copy the files over, and reboot! Then, enter the drive boot selection, and choose the UEFI USB entry, not the legacy one. No need for special tools or USB makers etc. The boot drive needs to be in GPT style. I'd actually recommend this for modern computers since it does actually boot differently .. Ideally you use a good (good doesn't mean overly expensive) fast USB 3.0 USB device, and use a USB 3.0 port. Installation of Windows will then be super quick. Of course, that assumes the use of a SSD.
So this is setting some registry values, right? Can you tell which ones exactly? I don't have experience with autohotkey so I guess Win10 will have RTM-ed by the time I find it out by myself
there are different branches working at the same time and the build machine runs all day long when necessary. Currently enterprise builds obviously gett'n on the list
It is like the times of leak are over. Microsoft will no longer tolerate the activities of leaking builds before they are released to those who are the intended testers. I don't think you'll know what they are about until somebody posts images as we have seen before the release of Windows 10 Technical Preview build 9841.
Who talk about leak ? I even don't care if the next version of windows 10 will be more 6 month. I talked about what I saw in the site that show the builds.
Sorry, if I misunderstood your post. What do you really want to know about without it been leaked before the release date? I am just curious to know how that is possible though. I care though because I am a Windows user. If the site intended (you are referring to) divulge the information about the build 9861 it means it has hold of the leak. Is that correct? But, my disagreement with Microsoft is that there are too many builds out there at the moment which are not so much different in any way beside the build versions yet the same kernel.
Just HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Accent\StartColorMenu The value set there changes when you select a new colour and the start menu will take its colour from that value. I converted the sample code given here (h*tp://msdn.microsoft.com/en-gb/library/windows/desktop/ms724892(v=vs.85).aspx). When WaitForSingleObject returns, a value under the Accent key has been set (so it gets triggered a few times for every colour change :\), so the script sets StartColorMenu to the desired value (in this case, the blue from my Windows 8.1 install), sends a WM_THEMECHANGED message to all windows to get Explorer to re-read the key and set the Start Menu colour and goes back to waiting for the next time the value changes. Granted, I don't really like sending WM_THEMECHANGED but the only other way I was effecting a change was by restarting explorer.exe...
Could be a million things. Kernel update, UI change, feature add/subtract. Who knows what changes from build to build (except those using it lol).