Thanks for your reply ... but I was interested in some specific problems you might have ... If there are other things to check, please let me know. I will keep the update in my OnePiece addon for now.

There are others who claim they have no issues as well, so no idea why some do and other do not. Here is some info I have found (other forums) for you to consider.

* This update is similar to 2 millions of gremlins
* Unable to create "New Folder"
* This security ID may not be assigned as the owner of this object
* taskbar stays at the top no matter how much locking, unlocking and dragging ...
* after unstall KB4074852, 2nd Ethernet connection has come back to life. Another symptom buggy oleaut32.dll
* oriental language characters still appear in the status bar when mousing-over "Open Containing Folder" in Windows search
* Wireless Network connection icon in the tray bar stay's on Not connected (Broadcom Connection manager)
* causes two GPF, in Bluetooth stack and HP Connection Manager
* failure with CDBurnerXP, wont start
* prevented GUI portion of Comodo Firewall from loading with message "COMODO Security Agent could not be started"
* error in starting "services.msc"

heinoganda: (Irony on) "If you say that you have no problems w/MSKB4074852 then I believe in Santa Claus"(Irony off)

Any software that makes use of "oleaut32.dll" could have issues with this update, its not just windows stuff. Also noted by a few that it did NOT show errors in while testing in Virtual Machine, but do in real life! The shear fact that so many people do have problems, is enough to stay away! (IMHO) Reverting to the older KB4018556-v2 is the safer bet!

I use "Big Pack Runtime Libraries by Wilenty 2018-03-24", does a great job with all the extra C++ and other stuff included there.

Do you have a link, not only for the app, but also a "home" page? I think he used to be at MDL, but from a quick look it seems that he had a disagreement with the staff there and he has pulled all of his content and disappeared. Unless he shows up again elsewhere, that might be the last version of the app available.

And do you also have a link for the "WinXP Enhanced Security Options guide", or have I just had a minor memory lapse?

There was some fighting between multiple peeps with Wilenty, they even took his stuff off of Majorgeeks, but it works just fine, at least the most current version I have. I will search for link elsewhere, post what I find

Hi All: I would just like to thank everyone here for there continued efforts to keep XP Alive!
_________________________________________________Here Are my collection of XP files that you can download.
i will update them when i can.https://mega.nz/#F!8nY0iBLK!JEwKcH9mYYy16iOuUrExyw

Hi All: I would just like to thank everyone here for there continued efforts to keep XP Alive!
_______________________________________ Here Are The XP files that you can download.https://drive.google.com/drive/folders/ ... sp=sharing
________________________________________

New time zone update today (KB4093753). Was creating the changelog when I decided to double-check the MU website. Hoping to release before end-of-day.

many thanks 5eraph for your addons

Hi All: I would just like to thank everyone here for there continued efforts to keep XP Alive!
_________________________________________________Here Are my collection of XP files that you can download.
i will update them when i can.https://mega.nz/#F!8nY0iBLK!JEwKcH9mYYy16iOuUrExyw

I'll do my best to stay on top of things, Nikos. Been disheartened the past few months hearing of AMD microcode bricking PCs and other bad updates from Microsoft. So, there were no releases from me for a few months to allow things to stabilize a bit. Can't promise I'll release monthly again, but I'll try.

Two Windows XP Embedded products will lose extended support in 2016, while two others face 2019 end-of-life dates, according to the post:

"Windows XP Embedded Service Pack 3 (SP3). This is the original toolkit and componentized version of Windows XP. It was originally released in 2002, and Extended Support will end on Jan. 12, 2016."

"Windows Embedded for Point of Service SP3. This product is for use in Point of Sale devices. It's built from Windows XP Embedded. It was originally released in 2005, and Extended Support will end on April 12, 2016."

"Windows Embedded Standard 2009. This product is an updated release of the toolkit and componentized version of Windows XP. It was originally released in 2008; and Extended Support will end on Jan. 8, 2019."

"Windows Embedded POSReady 2009. This product for point-of-sale devices reflects the updates available in Windows Embedded Standard 2009. It was originally released in 2009, and extended support will end on April 9, 2019."

Hi All: I would just like to thank everyone here for there continued efforts to keep XP Alive!
_________________________________________________Here Are my collection of XP files that you can download.
i will update them when i can.https://mega.nz/#F!8nY0iBLK!JEwKcH9mYYy16iOuUrExyw

Hi All: I would just like to thank everyone here for there continued efforts to keep XP Alive!
_________________________________________________Here Are my collection of XP files that you can download.
i will update them when i can.https://mega.nz/#F!8nY0iBLK!JEwKcH9mYYy16iOuUrExyw

Hi All: I would just like to thank everyone here for there continued efforts to keep XP Alive!
_______________________________________ Here Are The XP files that you can download.https://drive.google.com/drive/folders/ ... sp=sharing
________________________________________

There is an issue with KB4034775 that requires special treatment for that file. In 5erPOSUp.inf see lines 19 through 25, and lines 40 through 55 for more on how delayed file replacement is implemented.

Hi All: I would just like to thank everyone here for there continued efforts to keep XP Alive!
_______________________________________ Here Are The XP files that you can download.https://drive.google.com/drive/folders/ ... sp=sharing
________________________________________

Hi 5eraph.. will there be new July 2018 XPSP3_QFE_POSReady_Addon & IE8_Addon this month
many thanks in advance for an answer..

Hi All: I would just like to thank everyone here for there continued efforts to keep XP Alive!
_________________________________________________Here Are my collection of XP files that you can download.
i will update them when i can.https://mega.nz/#F!8nY0iBLK!JEwKcH9mYYy16iOuUrExyw

Ohh happy days... thank you 5eraph..
even though its sunny today.. you have brighten my day even more..

Hi All: I would just like to thank everyone here for there continued efforts to keep XP Alive!
_________________________________________________Here Are my collection of XP files that you can download.
i will update them when i can.https://mega.nz/#F!8nY0iBLK!JEwKcH9mYYy16iOuUrExyw

Simply changing an older file's version does not make the file secure, Nikos. That's the solution offered to trick the Microsoft Update website into believing the new version is installed. That's not good enough for me.

If you needed or wanted to use the files involved with the update, and you were content and were able to do so before the update existed, and applying the update caused something to break for you, then you are left with few options.

You can choose to not apply the update, as 5eraph and many others choose to do, hoping that eventually MS comes up with an update that does not have the problems that this one does for you. In the meantime, you will continue to be nagged to apply the update, unless you choose to hide it, and you will continue to use a file that is not "secure", from a threat that you might or might not ever run into, depending on your computing uses and habits and whatever other virus and threat protections that you employ.

You can choose to apply the update. You might be one of the lucky ones that are not effected by the various problems that many folks have reported after they applied the update. Or you might decide that being "protected" is more important than whatever problems the update causes. However, since MS obviously does not do the amount of testing with an update that they used to before releasing it, or to be fair the sheer number of different hardware platforms and software applications in use today make such thorough testing essentially impossible, can you be completely assured that this update really "protects" you from the existing possible threat or that it doesn't open up the possibility of a new threat that hasn't been discovered and exploited, ... yet? But hey, at least you won't be nagged to apply the update, and you will be as "secure" as everyone else that applied the update. On top of that, again, you might not ever run into the potential threat this update "protects" against anyway. And if MS ever does release an update that fixes the problems with this one, it should apply easily.

Or you can choose to apply a modified version of the update. The modified version uses an older version of one of the files involved in the update, with it's version number changed so that the OS, and MU/WU, does not know that the update has not been completely installed. As a result, you won't be nagged to install the update, and this modified version does not seem to cause the problems that the original one does. True, you won't be completely "secure" IF you ever run into the potential threat that exists, and IF that threat targets something that the modified file is involved with, and IF that treat can even effect you, depending on your computing uses and habits and whatever other virus and threat protections that you employ. But are you any less secure than if you simply did not apply the update? In this case I don't think so. In my mind, the risk is no different than if you hid the update. You aren't nagged to install an update, and you aren't completely protected from a threat that targets a particular version of a particular file. However, you will be able to take advantage of the "improvements", if any, in any of the other files provided in the modified update. And if MS ever does release an update that fixes the problems with this one, it should also apply easily.

So, while if I were 5eraph I would probably have included the modified update, he probably chose the safer option of not including either version, leaving the end user with the choice of which option to use. Only you, as a user of your system, with your OS and applications installed, knowing what your computing uses and habits are, knowing whatever other virus and threat protections you employ, and knowing the level of risk that is acceptable to you, can decide which approach best meets your needs. Regardless of which option you choose, any future update from MS should easily apply.

5eraph and bphlpt thank you for the detailed explanation about KB4134651.
The best option is for the end user to decide what to do.

Informative I do not use the known antivirus programs running constantly in the
background because I consider them to be a waste of resources.
Sometimes I use a portable antivirus program.
Every day there is a new virus or a "hole" in the operating system!!!
The best friends are "Deep Freeze", virtual machines and external backups.