heinoganda

But please not based on the kernel of KB4056615! An accidentally damaged patch.

@Dave-H @SD73 No problems, you had to force KB4056615 on your system with the parameter /overwriteoem. Have you ever had this problem? I can only recommend uninstalling KB4056615 and waiting for an update for KB4056615! Note: I do not want to make a random generator out of my computer!

I have uninstalled KB4056615 completely because apparently this update was not tested properly (probably no OEM release status) and behaves very strangely on some systems. I hope the MS responds and releases a new edition of this update. Apparently there were no more free computers by MS for the test's of KB4056615.

Key information was summarized in the first post of this topic (POSReady 2009 updates ported to Windows XP SP3 ENU). In this post is a reference to an older post from me where I went into the problem with the CPU utilization of the svchost process. Quite simply disable AU, when using WU latest cumulative update for IE8 should be installed / manually installed and when using MU in addition to WU if an Office package is installed manuel the latest updates (Microsoft Office Compatibility Pack, Office 2007 , for Office 2010 I have not done any test's yet). Currently it is known that every 2nd Tuesday in month the security updates of MS are released and one week later other updates.

Quite simply, KB4056941 and KB4056615 were released on 01/05/2018, the 3 updates for .NET Framework as well as the updates for Office on 01/09/2018.

That may be laughable at first, but I do not want to know how many employees have laughed at MS, where the code for svchost was tested (end of 2013), where the users have complained that because of AU/WU/MU the process of svchost.dll runs at 100% utilization. In January 2014 it was said that the problem was fixed with an update. Either I have not realized it, but this update is me guilty of MS until today.

In various forums, I unfortunately had to read that actually users do not install POSReady updates on their Windows XP, because it does not seem to work anymore. Thus, MS has staged the ideal scenario for itself.

Definitely an embedded system may not be used on a workstation PC and also no office may be installed! It was the end of 2013, where this abnormality was already present and adjusted a month later, I think rather that it was a test of MS! Basically it works, maybe not quite as MS imagined. In the end it does not matter, there is a workaround we can live with.

If you look more closely at the post, not only the download links have been specified, but also the susceptibility (CVE-2018-0748) was listed in KB4056615 with link to the Security TechCenter where the vulnerability is described. Regarding the Meltdown and Specter Vulnerability https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/ADV180002. Furthermore, I think that the Windows XP kernel does not provide complete native support for more recent processors. Therefore, I doubt the SpecuCheck.exe or a customized Speculation Control Validation PowerShell script could even work properly. Since my latest processor is only an Intel Core 2 Duo E6420 and has no sideband technology, I can therefore make no specific statement or test. Fact is that KB4056615 is still flawed and leads to problems where it emerges from the previous post. Then the problems when a virus scanner is not working properly, what is difficult to understand? If a virus scanner with the file system NTFS leads to malfunctioning with the copying of files, there should better not be installed updates concerning the Windows XP, nobody wants a BSOD. @Dave-H If Windows 7 - Windows 10 is affected by a third-party virus scanner, it must be up to date and the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\QualityCompat "cadca5fe-87d3-4b96-b7fb-a231484277cc"=dword:00000000 should be present for the security update to become available due to Meltdown and Specter. However, there are problems with older AMD processors, where it can lead to a BSOD!

1. If a virus scanner malfunctions, so that some files on an NTFS volume can not be copied, then this problem could also occur during the installation of updates. Here is again improved by side Avast, another μUpdate is provided. That means I would wait until the problem is solved or uninstall the Avast version 17.9.3761.0. 2. KB4056615 is causing more or less problems, as already written in this topic. In my opinion, a not yet properly tested update where apparently still has no OEM status. I will wait for a follow-up update, although there were no specific problems on my system. 3. Ultimately, you have to decide for yourself if you take the risk because of the first problem that an error occurs, the same also applies to the second point.

I think that the major changes to the kernel sometimes cause problems with some processors. Best then uninstall KB4056615 and wait for what will appear on the upcoming patch day for updates. Rome has not been built in a day.

@glnz or own risk Beta Version note: Therefore, probably the problems come with your Excel file.

@glnz Had you asked to download the file directly from Malwarebytes (mb3-setup-consumer-3.3.1.2183-1.0.262-1.0.3374.exe) and then copy them into a folder as you like on the hard disk!

@glnz Just download and copy to any folder on the hard drive, do not install!

In %windir% or C:\Windows.

On my three computers, I had no problems installing KB4056941 and KB4056615. I can not retrace at the moment unfortunately. Have you ever looked in the log files of KB4056941and KB4056615 or in the event viewer to see if they are noticeable?

@Dave-H @SD73 There seems to be an incompatibility of the kernel with hardware. Will try on various hardware. A hardware list would be an advantage, maybe there similarities which point to the problem.

@glnz Just download Malwarebytes and copy it to another folder. If that works, I would risk it.

Major changes have been made to the kernel, which will require MS to make changes to some components as well, such as the ATMFD.dll and NTFS.sys files (there will certainly be some updates, by the way, NTFS.sys, the first official patch since appearing from SP3). Now software such as virus scanners or the behavior of programs (MalwareBytes Anti-Exploit, EMET ect.) that interact at the kernel level can get malfunctions that are not apparent at first. Note: I do not want to know which barrels were opened! @SD73 In your place, I would download KB4056941 and KB4056615, disconnect network, disable Ad-Aware Free Antivirus and MalwareBytes Anti-Exploit, and reinstall the two updates! Press the thumb it works! http://download.windowsupdate.com/c/msdownload/update/software/secu/2017/12/windowsxp-kb4056941-x86-embedded-enu_24ebcc41e3f03048c25cf02d8d8ab6107479aabd.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/12/windowsxp-kb4056615-x86-embedded-enu_2ce39329b6854ba3fb28eba1847a15a39c4709be.exe @FranceBB Based on the updates (NTFS.sys), I think the Avast with the version 17.9.3761.0 appropriate security measures taken in Windows XP meant that no more files can copy properly. At a later date I will try again at an official update by Avast.

@glnz If you have Avast version 17.9.3761.0 installed, I can only advise against it at the moment! Either uninstall Avast or wait for the update to be released for Avast, where the bug will be fixed where various files can not be copied! It is not enough to deactivate!

Look at the electric garbage mountains grow. MS already sees the $ signs in front of the eyes. The stupid is once again the consumer. Who thinks about new hardware at this time, comes from the rain in the eaves. Update 01/05/2018: Have looked in my crystal ball, probably the following updates (based on the published updates for Server 2008 on January 3, 2018) will appear for POSReady: Available since 01/05/2018 KB4056941 KB4056944 KB4056942 KB4056759 Available since 01/05/2018 KB4056615 (Kernel and NTFS file system update / CVE-2018-0748) KB4056568 (Cumulative security update for Internet Explorer) The beginning is done, the rest will probably be released no later than Tuesday! http://download.windowsupdate.com/c/msdownload/update/software/secu/2017/12/windowsxp-kb4056941-x86-embedded-enu_24ebcc41e3f03048c25cf02d8d8ab6107479aabd.exe http://download.windowsupdate.com/d/msdownload/update/software/secu/2017/12/windowsxp-kb4056615-x86-embedded-enu_2ce39329b6854ba3fb28eba1847a15a39c4709be.exe

Let's wait until the official patchday. For another, a BIOS update is needed depending on the hardware. Especially with older hardware, this could be a problem. There are some virus scanner issues with the custom kernel. On the other hand, not all gaps are closed with the current emergency patches.

Starting with Avast version 17.4.3482.0, the offline installer only works with online connection on Windows XP and Vista. Here the network connection must be disconnected at the right time during the installation, otherwise the latest version of Avast will be updated. No easy venture! Avast is aware of the bugs that occur on Windows XP and is working on an update for version 17.9.3761.0! For Intel processors that include the virtualization feature VT x technology there is a vulnerability. Furthermore, according to Google, AMD (restricted) and ARM processors are vulnerable. There are two attack scenarios developed by security experts that were baptized Specter and Meltdown respectively.

@glnz Can I remember that you have installed Avast. Have a problem with the current version 17.9.3761.0 found that when copying some files that copy infinitely and not come to the conclusion of the process (noticed in the files mb3-setup-consumer-3.3.1.2183.exe and mb3-setup-consumer-3.3 .1.2183-1.0.262-1.0.3374.exe). Disabling Avast did not solve this problem, so I installed an earlier version (17.5.3585.0) of Avast where this problem does not occur. There have been problems with Office programs on Windows XP in earlier versions, with older versions of Avast. It seems that the current version of Avast has once again become a problem. Currently, the offline installers of Avast under XP can only be used to a limited extent! Best remedy, it should be created before the update of Avast (only manually update) an image of the installed XP.

Have a German Windows XP used, for this reason, this format of the date displayed. So you do not get sleepless night.