Jump to content
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble
Strawberry Orange Banana Lime Leaf Slate Sky Blueberry Grape Watermelon Chocolate Marble

MSFN is made available via donations, subscriptions and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, register and become a site sponsor/subscriber and ads will be disabled automatically. 


heinoganda

Member
  • Content count

    526
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

150 Excellent

About heinoganda

Profile Information

  • OS
    none specified
  • Country

Recent Profile Visitors

4,226 profile views
  1. Of course, you would need to install IE8 before the IE8 cumulative update can be installed, which includes updates that were previously offered separately (hlink.dll, inetcomm.dll, jscript .dll and vbscript.dll).
  2. @jaclaz The last update for IE6 was KB3124275 from 01/11/2016, the problem with svchost.exe appeared from November 2016 on and means that from this point on when using WU in advance manually the most recent cumulative update for IE8 should be installed. In addition, if you are using MU, you must have the relevant Office Compatibilty Pack / Office 2007 updates from November 2016 to date so that svchost.exe's high processor load does not occur. Note: If you also use POSReady updates for Windows XP sp3, it is also advisable to install the cumulative update for IE8, because the components for Microsoft Office 2000 (hlink.dll), Microsoft Internet Messaging API (inetcomm.dll), JScript (jscript .dll) and VBScript (vbscript.dll) are no longer available in separate updates.
  3. On the subject of Meltdown and Specter, according to this test, an Intel P4 is affected. Unfortunately, it is the problem that Intel still AMD published a more detailed list of affected CPU's. A patch for Windows can unfortunately mitigate this problem, even if the BIOS / UEFI the microcode was patched, the real problem remains. Only a new CPU helps where the architecture no longer allows these forms of attacks.
  4. For external media (stick, flashcard and old good mechanical hard drive) I use exFat. Anyone who has already dealt with this file system should, like me with an external HDD, see this file system as an advantage. With various defragmentation tools I noticed that the data was never fragmented.
  5. But please not based on the kernel of KB4056615! An accidentally damaged patch.
  6. @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!
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. 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.
  12. 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.
  13. 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!
  14. 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.
  15. 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.
×