So yeah. Still having issues after System Restore (taken immediately after installation). WindowsUpdate.log attached. Anyone?
I am relatively sure this update hosed my PC, after installing it, my Display flickered endlessly and I could not log in to my main account. I could not enter my password, the screen kept whiting out before I could enter my password. I had to do a system restore.
I need to avoid this one, but even with Deferred installation, they eventually go in. Whatever the blazes this update is for, I had to do a system restore. Thankfully I had a restore point from this morning.
SOLVED!
C:Users <==> U: (separate users and system)
The clue was the 0x80070001 return code from the installation. All is well.
Steps:
- cd users
- robocopy /mir /zb Public C:Public
- regedit
- save HKLM
- search for UsersPublic, replace with Public
- restart
DONE. No update problem!
[Now to re-do everything I customized and save another system image... and turn on backups on U: ...]
Of the 3 machines, only the laptop (upgraded) fail to install this kb3081444. So did a manual download to fix the issue. Guess Microsoft still not getting their update engine to run smoothly.
Updates? What's that?
In my opinion, you're lucky if KB3081444 fails to install. A successful installation for me put me into a repeating cycle of refreshing the screen and reloading icons on the desktop and taskbar. Any windows you open (file manager, Microsoft Edge, Media Player, etc.) just close on their own with no warning or error.
I did a system restore to back this out.
BJohnson, you hit the fookin' nail on the head, it's a BAD UPDATE. I have been reading about this issue all over the net and 1444 caused it. In my case, I could not even log in, cos my screen would not stay stable long enough for me to enter my password.
When I was lucky enough to enter my password, it failed to log me in and it would just kick me out back to the Lockscreen. I was very lucky to have made a system restore point just previous to allowing that crappy update in. I logged in to the Insight app and I sent a fervent request for them to put the updates back to the way they were from XP through 8.1, where we could CHOOSE to ignore them and install them when we want, not after every damn reboot.
I agree. My laptop just re-applied KB3081444 (can't put off doing a restart forever thanks to other updates from Java and AVG Antivirus). It is now behaving like before. I cannot see any way to avoid having Windows Update apply this fix, either. There must be a lot of people unhappy with Win10 right now. Whatever percentage of folks who are also having issues with this fix will likely be heading back to Win7/8. This will be a black eye for Microsoft that will cost them in the long run.BJohnson, you hit the fookin' nail on the head, it's a BAD UPDATE. I have been reading about this issue all over the net and 1444 caused it. In my case, I could not even log in, cos my screen would not stay stable long enough for me to enter my password.
When I was lucky enough to enter my password, it failed to log me in and it would just kick me out back to the Lockscreen. I was very lucky to have made a system restore point just previous to allowing that crappy update in. I logged in to the Insight app and I sent a fervent request for them to put the updates back to the way they were from XP through 8.1, where we could CHOOSE to ignore them and install them when we want, not after every damn reboot.
I will do another system restore and hope they have a new cumulative update soon to fix what broke in 1444. If I have to do it again, it will be to revert to Win7 while I still can.
good tihng i have windows 8.1 on my laptop..
After reading about hiding updates but seeing that this is not an option for Windows 10 Home, I am going back to Windows 7 once the third system restore completes. What a bone-headed move by Microsoft!
