New
#10
Cumulative Update KB4103727 Windows 10 v1709 Build 16299.431 - May 8
-
-
New #11
This was a fast and easy install on my Lenovo laptop, but my husband's HP had problems--he got a message "personalized setting not responding" and then a black screen. I brought up task manager with ctrl-alt-del and saw that nothing was running; signed out using task manager, and a sign-in screen came up immediately. And then everything was back to normal. WU showed that KB4103727 and accompanying Flash update installed successfully.
-
New #12
Both, the KB4103727 and Flash update installed successfully yesterday. Late last night, I've got this general error message:
This is the first time the system in question had this error. There's not much to go on to identify the source of the bug check, since there's no hex numbers, etc., displayed on the screen. The system restarted without any issue and has been running just fine for now.
The chances are that bug check could be related to the update and by proxy, some of the drivers may require update. How can I identify the cause of this bug check?
TIA...
-
New #13
I've looked at the mini dump file via BlueScreenView and it shows the bug check code:
That's pretty much verifies that the BSOD is the result of the KB4103727 update. Not much to do, just wait for the June updates, since I don't intend to update to 1803 anytime soon...
-
New #14
OK I made another post but I will also copy and paste here since it's related :)
I'm avoiding 1803 too since I really don't care for this changes!
Funny thing is I manually checked for updates, Windows 10 April 2018 Update was found but since I always leave my connection to metered it didn't download the file. So I just left it alone and for like 3 days Windows would make a defender pop up saying I should update but I ignored. Now it does nothing and just gave up it's like there is no important update anymore hahahahaha
I can be wrong but I just choose to wait even more after it. Feels like Microsoft decided to not push it to me because a lot of ppl is having problems :)
What do you guys think?
Now since this is the first time I avoid a update like this I never even knew they gave support to old versions!
Today Windows automatically showed me this KB4103727 and I got confused :) I googled it and some ppl are having problems, in here some seem to have problems too soooo what should I do? Can I just ignore this one like I ignored 1803 and it will go away? :)
This updates should be better as time passes but they seems to get worse
EDIT: Well KB4103727 was forced on me and nothing bad happened yet! Still WU is not finding 1803 anymoreLast edited by Needhelpwithwin; 12 May 2018 at 12:47.
-
New #15
-
New #16
Yep! No ones is safe :)
-
New #17
At least two reasons:
a. Not all users are upgraded to the next build at the same time- may take several months.
b. Pro upwards can DEFER upgrades, so may take e.g. 365 days before the build upgrade is applied. (Gives admins, businesses, an users a degree of control and stability e.g.).
Quote
Related Discussions
