My1 Posted February 3, 2015 Share Posted February 3, 2015 they seemingly added the reg Tewak that usually only internal MS ppl should use into the update, and that create the loop with the non-downloadable new builds... Link to comment Share on other sites More sharing options...
NoelC Posted February 3, 2015 Share Posted February 3, 2015 No, that's not it, not entirely. I'm well past that faux pas. There's no ability to hide updates. I have an update that can't be applied, probably because it's for an old Microsoft application where the update doesn't make any sense any more (something about fixing a .NET 2 bug). The same thing would occur if, for example, a display driver update were made available but you keep your drivers up to date yourself by visiting AMD.com or nVidia.com and you don't want it. -Noel Link to comment Share on other sites More sharing options...
My1 Posted February 3, 2015 Share Posted February 3, 2015 that's junk... Link to comment Share on other sites More sharing options...
NoelC Posted February 3, 2015 Share Posted February 3, 2015 By the way, I've just verified that re-enabling the "classic" Windows Update interface (via registry tweaks) and hiding the updates that are failing repeatedly does NOT hide them from ongoing attempts to download once the new UI has been reinstated. -Noel Link to comment Share on other sites More sharing options...
JorgeA Posted February 3, 2015 Share Posted February 3, 2015 By the way, I've just verified that re-enabling the "classic" Windows Update interface (via registry tweaks) and hiding the updates that are failing repeatedly does NOT hide them from ongoing attempts to download once the new UI has been reinstated. -Noel Didn't Microsoft recommend against making this registry tweak, on the grounds that it might break 9926's ability to download/install future builds? (Or something along those lines.) How would one undo that registry change? --JorgeA Link to comment Share on other sites More sharing options...
NoelC Posted February 3, 2015 Share Posted February 3, 2015 Yes, that's why I set it back. It's just two values in two different nearby keys. This sets "the old way" Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX]"IsConvergedUpdateStackEnabled"=dword:00000000 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings]"UxOption"=dword:00000000 This sets "the new way" (which is clearly unfinished) Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX]"IsConvergedUpdateStackEnabled"=dword:00000001 [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\WindowsUpdate\UX\Settings]"UxOption"=dword:00000001 -Noel Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now