SD73

On a fluke I checked the Office 2003 catalog and there's one there for us older users too.

The catalog shows 3 Framework updates are available. My MU has been running for a while now and hasn't picked them up yet. I'll let it run a good portion of the day just to see what happens. If nothing by the EOD, I'll just manually download them.

Click on the "Last Updated" cell on that page and it will sort the new ones you're looking for to the top. Or alternatively search a few posts back and you'll find direct links to the downloads posted.

And thank you again for taking that brave first step. MiXiT get's some bonus points too in my book. I had one other patch that for years showed as installed in my add/remove programs but Update would always show it as not being installed, so I finally hid it. Well after learning about the over write oem switch I figured what the heck, let's push my luck once again. Sure enough, not only did it install fine, but now there are no more hidden updates needing to be installed.

Thomas. for what it's worth I tried your suggestion and it did not work. On a lark, with Mixit's idea to use force switch, and Dave's bravery to step forward with giving it a try I did the same. IT WORKED! After rebooting the kernel files were updates and Microsoft Update did not list that as an update needing to be installed.

Dave, I've read that at least with Win 10 the update won't be offered if it finds you have a virus program or something else that's not compatible with the new kernel. You may want to check some of your ancillary programs for updates and try again or wait it out a bit as something more compatible may be in the pipe.

I'm glad that didn't break anything, Dave. Keep us posted as you test it some. I think I'm going to sit this out now based on Destro's explanation. However, if an updated release that doesn't need to be forced through comes out, I'll let it work it's magic. BTW, Dave, did you confirm if you have an FSB chip?

Thanks Destro, I think if I'm understanding you correctly and not overthinking this, I am safe. I believe I do have an FSB processor. Intel® Pentium® Processor E2180 1M Cache, 2.00 GHz, 800 MHz FSB

Ah, gotcha. Thanks! I suppose I could look for the older file, or just be lazy and wait. I'm hoping laziness pays off, because I'm afraid of the consequences in this case.

Roytam1, can you explain what you mean by reverting to 5512?

Yes, but it was destroyed in a day. I'll do just that as I'm out of options at this point.

LOL, well there goes my big plan. I was hoping another patch would be released. Oh well. I've tried all the other suggestions and still no love for the #615 kb.

I've got those in my log too! I'll wait to see what happens AFTER Dave puts his toes in the water.

Good idea. Nothing unusual in the Event Viewer. I looked for log files in the SoftwareDistribution folder pertaining to the failed KB4056615, but I couldn't find one. Is there a specific place to check for KB related logs?

Good observation, heinoganda. I'm running a Dell Inspiron that's about 10 years old. It's a model 530s w/dual processors - Pentium Dual CPU E2180 @ 2.00GHz.

Well, at least you saved me some time trying to do the same dual boot trick since mine also has Linux. I suppose we still have Patch Tuesday to look forward too. I wonder how many others are having this problem but haven't noticed it yet? And Dave, how is it you have a Kernel with a slightly higher version number than me?

Safe Mode did not update the Kernel files either....

Hrmmmm. I'm may be worse off than you, Dave. Both my Kernel are 5.1.2600.7053. I ran both the updates from the downloads this time after I disconnected from the LAN, and disabled both my malware softwares. They both installed without issue; however, when i checked Windows Update it still said KB4056615 was missing.

Interesting! I will try the man with a capes suggestion, heinoganda and report back.

My update went semi-smooth. The Windows Update found both KB's and installed them fast. After the reboot I ran Update again and it said kb4056615 was needed. I checked Belarc and it reported it was installed and I verified it was in Control Panel / Programs. So I just hid the warning in Windows Update. Also, I had no conflicts with Ad-Aware Free Antivirus+ or my MalwareBytes Anti Exploit. And like Dave, I have not noticed a performance hit, but I do little on this machine. My 2 updated Windows 10 Machines seem to be about as fast as well and no conflicts with anything else I'm running. Thanks guys and keep on XP'ing!

This is a big one. The only silver lining is AMD aren't affected and CPU's older than 10 years may not be either. My XP machine is in the secpmd category, but my other PC's are more recent Intels. It'll be interesting to see how this plays out.

Designed to make sure he doesn't miss the Cybersales going on this week.

Thank you my friend. Save the medicine for next month. I may need it!

Yep. I wasn't concerned about those two. I'm glad my PC was smart enough to avoid them as the last thing I want to see when it boots are those messages. Now I'm looking forward to next months updates to see how smooth they go. Thanks again, fellas!

They are listed as... HOTFIX ID: EOL-MIICROSOFT-WINXP EOL-MIICROSOFT-OFFICE03