Discussion in 'other software & services' started by emmjay, Aug 15, 2016.
Thanks emmjay. I ll check the tasks.
Excellent advice and instruction, emmjay! Thank you. I disabled both scheduled tasks. I love getting the jump on Microsoft when they are gearing up to nag me.
Noticed that KB4503548 Net Framework 4.8 has been sitting in the optional queue, recommended/unchecked for both W7x86 and 64 since 8/13/2019. I think this update was originally released in April 2019. I understand that developers and/or sysadmins might make use of it and that is partially why WU sent it out as optional. It is gathering dust, however, like all other windows updates it will be gone in 2 weeks.
Sure would like to know what others here have done with this patch.
I hid it on both W7 and W 8.1 as none of my apps need it.
Same here, but I did not bother hiding it.
Added: I see that it is an update to KB4019990, d3dcompiler_47.dll (9/2017). This is a prereq, though not stated in the knowledge base info.
On Win 7 64-bit:
- KB4503548 https://support.microsoft.com/en-us/help/4503548
Not offered, not installed as far as I know or could find. Was it maybe included in another patch?
- KB4019990 https://support.microsoft.com/en-us/help/4019990
Installed on 13 Sep 2017
- The latest .Net Framework I installed:
Security and Quality Rollup for .NET Framework 3.5.1, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.7, 4.7.1, 4.7.2, 4.8 for Windows 7 SP1 and Server 2008 R2 SP1 (KB4533095)
PS: looking at KB4503548 Microsoft .NET Framework 4.8 offline installer for Windows
Microsoft .NET Framework 4.8 for Windows 7 for x64 (KB4503548)
When you go from there to the download page, you get three installers :
Is there a test someplace to confirm that the blasted servicing packs for SHA-2 are actually functional on my computer?
I ask because Windows 7 works fine until I install the December patch KB4530734 where it fails to verify digital sig of winload.exe, the error is 0xc0000428. Details in my post#891.
Once I recover an image, all is well again.
Assuming you can't fix it, is it practical to disable internet in Win7 and use internet in Win10. You can still use Win7 apps.
I mentioned this in a separate post - try removing the multi-boot, keep only the windows bootloader.
See if that helps - I had an issue with this on in a dual-boot config - with the Sep sha2 update.
Absolutely ... well, Wilders has to ba accessible from all systems forever
I was thinking along those lines as well, BUT if M$ decides at some point in the future to send us a patch, similar to what we got for XP for petya, wannacry, etc, years after they stopped support, I want to have a system that CAN update with the SHA-2 job running. Just in case I venture out beyond Wilders looking for some help.
I do switch between the systems. Restarting Win7 from the Grub menu is fast. But restarting Win10 is a sloow pain due to, I think, resolving the chain, so it's another reason I'd like to have it all working.
Thanks. I had no problem installing KB4474419 in September, though it did fail in April, reverted, and then worked from Admin login. So if that's what you speak of isn't my problem, me thinks.
Removing the dual/triple boot scares me to death. Not sure I follow your instructions in your post on your site. Will try again later to understand.
You probably don't want to change your setup but if you ever decide to have more than 4 primary partitions (on that drive) containing OS then you can use BootIt BM as a Boot Manager. It doesn't use grub in the MBR. Grub is in the Linux partition.
Thanks for the suggestion, but I think I'll pass. I read about Bootit BM and it scared me.
BTW, the alignment fixings you helped me do a year or so ago has been working well.
I didn't believe one word you said, but tried it anyway.
With Grub2 bootloader gone KB4530734 finally installed
It's possible that KB3133977, a BitLocker patch which I don't need but Woody mentioned, might have helped.
We'll never know.
We will - it's the bootloader update in the Sep revision - I would never suggest anything I've not tried myself.
I know you would not.
But you wrote about a different update than what I struggled with - KB4530734, with error 0xc0000428. And I did not see the relation.
The September issue of KB4474419, installed just fine under grub2. It did fail and reverted several times in March but with a different error, 0x8... something, which apparently was a permission issue.
So I was just not sure if your kill-grub loader suggestion was applicable. Understand my confusion? Just trying to learn few tidbits here.
How did you know that KB447419 changed boot manager?
I agree it is scary and has a steep learning curve but we are here to help if you pluck up the courage.
act8192, it says in the release notes for the kb.
I am so glad to hear that you finally got this sorted. Your plight has tormented me for days. GRUB corrupted by Windows updates has always been an issue in multi-boot situations - there are many instances reported but it is so hard to nail down the offending patch.
Funny that you mentioned KB3133977 - the knowledge base info was extremely inadequate but I do think it was a player in your situation. I am beating myself up for not mentioning it to you earlier. I had written it down and wanted to relay my thoughts on it but I drew back because I was unsure. Our resident Linux expert was your better source at that time as he had experienced the bootloader issue himself.
FWIW: For users who want to keep W7 after eol, and looking at dual boot, it is best to implement that after Jan 14, 2020 to avoid software maintenance update conflicts.
Windows by the numbers: Windows 10 resumes march towards endless dominance by Gregg Keizer.
Here's what will happen to your Windows 7 PC on January 15, 2020 by Mary Jo Foley.
Another SSU (Jan 14, 2020) for W7, KB4536952.
The KB states that it replaces the November and December SSUs.
NB: It will be delivered through windows update (as usual the 'important' queue has to be empty for it to show up).
So basically if I update MS infects my machine
Something like that.
Separate names with a comma.