Batu69 Posted February 17, 2016 Share Posted February 17, 2016 Several reboots might be triggered by this update Another day, another broken patch released by Microsoft, this time causing problems on computers running Windows 7 and Remote Desktop Protocol 8.0. One of the updates shipped by the software giant as part of February 2016 Patch Tuesday seems to be pushing Windows 7 computers into a longer reboot loop. Microsoft has already acknowledged the problem and explained that “you may have to restart the computer multiple times after you install this security update on a Windows 7-based computer that is running RDP 8.0.” Security improvements The update at fault is KB3126446, and the company provided it to fix security vulnerabilities in Microsoft Windows, as part of bulletin MS16-017. The issues, however, are only experienced on Windows 7 computers updated to Service Pack 1, but the patch is also delivered to Windows 8.1 and Windows Server 2012 R2. “This security update resolves a vulnerability in Microsoft Windows. The vulnerability could allow elevation of privilege if an authenticated attacker uses Remote Desktop Protocol (RDP) to log on to the target system and sends specially crafted data over the connection. By default, RDP is not enabled on any Windows operating system. Systems that do not have RDP enabled are not at risk,” Microsoft says. Basically, what it could happen after installing the update is for your PC to reboot several times, but the number of restarts is not yet specified. But once this reboot loop comes to an end, you should be able to start re-using the computer normally, with no other issues likely to be caused by this update. Certainly, having the machine rebooted several times is not what you’d expect when installing an update released by Microsoft, but you should actually accept it because, after all, it could be worse. This month’s Patch Tuesday turns out to be a fiasco, with several Windows 10 users also complaining of problems caused by cumulative updates released by the company. Article source Link to comment Share on other sites More sharing options...
ASIO Posted February 17, 2016 Share Posted February 17, 2016 using 7 sp1 from 2011 without update no problems till now. Link to comment Share on other sites More sharing options...
Pete 12 Posted February 17, 2016 Share Posted February 17, 2016 Me too,on Win7, no udates=no pain............. Link to comment Share on other sites More sharing options...
Holmes Posted February 17, 2016 Share Posted February 17, 2016 What does the name of the update say if you look at windows update history? I want to know so I can avoid this. Link to comment Share on other sites More sharing options...
Pete 12 Posted February 17, 2016 Share Posted February 17, 2016 Did you find KB3126446 in the update-history ? Yes= maybe better uninstall ,troubles may occur No= your safe Link to comment Share on other sites More sharing options...
vibranium Posted February 17, 2016 Share Posted February 17, 2016 It took two reboots on my machine. I freaked out for a moment. Link to comment Share on other sites More sharing options...
PrEzi Posted February 17, 2016 Share Posted February 17, 2016 It does the same in Win 8.1 too --- my two PCs didn't had any problems with multiple reboots, but the third one rebooted like 4 or 5 times.... I was also freaking out that I would need to restore to an earlier state, fortunately was fine afterwards. Link to comment Share on other sites More sharing options...
steven36 Posted February 17, 2016 Share Posted February 17, 2016 3 hours ago, vibranium said: It took two reboots on my machine. I freaked out for a moment. This update came out Feb 9th i installed on a windows 7 laptop Feb 10th i got the the same it rebooted 2 times and now its been a week and its fine. Link to comment Share on other sites More sharing options...
Holmes Posted February 17, 2016 Share Posted February 17, 2016 I know to look for KBthirtyonetwentysixfourfortysix I wanted to know the full name I thought you couldnt sort by KB I thought I couldnt I figured it out Im good. Link to comment Share on other sites More sharing options...
steven36 Posted February 17, 2016 Share Posted February 17, 2016 @Holmes you didn't do updates on patch Tuesday for FEB yet ? If you did and you're not having problems there's no need to uninstall it . The issues it caused was minor when you applied updates all it done was instead you're PC having to reboot once it rebooted 2 times. by the time this news was posted here these updates were over a week old Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.