heinoganda
Content Type
Profiles
Forums
Events
Posts posted by heinoganda
-
-
Have you ever tried to create and test the batch file from the following link?
Otherwise, a suggestion, if you have the opportunity to create a virtual machine with, for example, VMware Player and a Windows XP sp3 to install, I can gladly provide my update rollup where you can thoroughly test whether this error also occurs (you can then gradually install their usual programs to possibly see from when the error occurs).
Complement:
Because of the outdated authrootstl.cab from 22nd September 2017 look here at times when the file authrootstl.cab should be, this problem has already been discussed in this topic and also there is therefore the current Certificate Updater 1.3 an additional feature (please read info version 1.3.txt).Incidentally, I have set the IE 8 only TLS 1.2 for encryption.
0 -
Maybe it's the outdated Eudora or other software. In any case, "something" where this obsolete certificate requires that is no longer available.
0 -
1 hour ago, Dave-H said:
I fixed my .NET update problem by installing .NET 4 Extended, problem solved! Quite why I would need it I've no idea, but I have got it on my main machine anyway, I obviously never bothered with it on my netbook.
At the latest after I installed a program that needed .NET Framework 4 and still did not work, I only install .NET Framework 4 complete with Extended. Maybe you ask MS why only .NET Framework 4 Client is offered via WU / MU. I also noticed that there was still no update for only .NET Framework 4 Extended, maybe the error is AU / WU / MU, where no difference is made with Client or Full (Client and Extended).
Is for me one of the reasons why I create my own update rollups. If I had not been so busy the last few days myself with my update rollup, I would have offered you now a complete .NET Framework 4 package (with updates) where no eternity needed for the installation.
0 -
Meanwhile, it is known that it comes with various factory OEM installations of Windows XP problems when installing updates where kernel mode files update (KB4458318 ks.sys Kernel CSA Library, KB4230467 ntoskrnl.exe ntkrnlpa.exe NT Kernel & System). As a remedy to install the update, manually install the update with the -o parameter (overwriteoem). Various "protection software" can also cause these updates are not installed correctly.
0 -
Thanks for the info, will complement the entry in the config.ini for future updates on HTTPS proxy. This information helps to improve the functionality for all users of HTTPS Proxy.
Annotation:
Alone I can not test all websites / programs in this world for the function with HTTPS proxy.
1 -
1. For Winows XP there are no regular updates for MSE at Microsoft Update, except the POSReady key is entered in the registry (see here).
2. Is there an updater for MSE for download and update the definition (see here).
3. If the first two options are unwanted, the following registry entry for MSE may be changed, where updating under MSE Update will be limited again.
(Attention, it should only make users who are familiar with permissions!)from [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Antimalware\Signature Updates] "FallbackOrder"="MicrosoftUpdateServer|MMPC" to [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Antimalware\Signature Updates] "FallbackOrder"="MMPC"
0 -
Update for root certificates:
New:
CN = emSign ECC Root CA - C3
O = eMudhra Inc
OU = emSign PKI
C = USCN = emSign ECC Root CA - G3
O = eMudhra Technologies Limited
OU = emSign PKI
C = INCN = emSign Root CA - C1
O = eMudhra Inc
OU = emSign PKI
C = USCN = emSign Root CA - C2
O = eMudhra Inc
OU = emSign PKI
C = USCN = emSign Root CA - G1
O = eMudhra Technologies Limited
OU = emSign PKI
C = INCN = emSign Root CA - G2
O = eMudhra Technologies Limited
OU = emSign PKI
C = INAdded again:
CN = Entrust Root Certification Authority - G4
OU = (c) 2015 Entrust, Inc. - for authorized use only
OU = See www.entrust.net/legal-terms
O = Entrust, Inc.
C = USThose using heinoganda's Cert_Updater.exe should run it ASAP. Others needing a redistributable rootsupd.exe should follow his instructions for creating their own, or PM at 5eraph for an updated EXE file.
1 -
I just tested Mega and could not detect this error (tested with Google Chrome 49.0.2623.112). Have changes been made to the "config.ini" file? Are your Windows XP Root Certificates up-to-date? Is the entry in the file "config.ini" present under [SSL Pass-Thru] *.mega.co.nz? Quit HTTPS Proxy, delete the contents of the "Certs" folder, and then restart. Maybe you give me the link via PM, where I can check where the error lies. Unfortunately, there is no news for Python when it comes to supporting TLS 1.3.
0 -
HTTPSProxy works only 100% on the local machine. If HTTPSProxy is made available on another machine or server there is a problem with the least time difference.
1 -
Google Maps that is no longer working with older IE is called at f.lux location, there is no other standard browser because f.lux always works on the existing IE.
Reset the proxy settings from the system (IE) if quit ProxHTTPSProxy, start "ProxHTTPSProxy_PSwitch.exe" and quit ProxHTTPSProxy again did not work!
0 -
With the program f.lux is called in the attitude of the locatian over the IE Google maps, which in the IE7 / 8 no longer functions. Quit ProxHTTPSProxy, start "ProxHTTPSProxy_PSwitch.exe" and quit ProxHTTPSProxy again. This will reset the proxy settings to the former settings of the IE. If you're using a proxy switch (127.0.0.1:8079) on Chrome, then "ProxHTTPSProxy.exe" should be used to start ProxHTTPSProxy.
0 -
About the topic that in Google Chrome various encrypted websites can not be opened with the error message ERR_SSL_VERSION_OR_CIPHER_MISMATCH has been discussed many times in the forum. This is because Google Chrome accesses the certificates of Windows XP where ECC certificates can not be processed and stored in the certificate management of Windows XP. Therefore, my offer for a local HTTPS Proxy with which these web pages can be opened. (If interested, send me a PM.)
Meanwhile, IE8 also supports TLS 1.2.0 -
New build of ProxHTTPSProxyMII (Rev 2m) available. Various python modules and CA certificates (cacert.pem) updated. If interested, send me a PM.
0 -
22 minutes ago, FranceBB said:
I never thought I was gonna see the yellow shield automatically popping up in my tray again, but it seems I will, starting from next month.
But would still not install the updates with automatic updates, there I recommend this anyway with the IE to search so that the user has control if a faulty update is offered.
1 -
2 minutes ago, Bersaglio said:
Guys, I'm very glad to help with direct links. I will try to publish these links in the next 7 months too!
I did not mean that you should not publish the direct links, only I think it's worth mentioning.
0 -
Positive news, I noticed when testing my update rollup, in the cross check with WU, the WU / MU works again and no extreme CPU utilization of the process "svchost.exe" generates. A test at the level of December 2017 also showed that this problem no longer exists (no current cumulative update of IE8 manually installed). The WU / MU website is also working reliably again.
3 -
51 minutes ago, wyxchari said:
There will be no more Windows updates for processors without SSE2 (Pentium III, AMD Athlon XP and earlier) for all operating systems. Microsoft has said it for Windows 7 although its support ends in 2020. For Windows XP Embedded has not said anything.
POSReady 2009 was, as the name implies, released in 2009, at that time I did not have a cash machine or cash register system where processors were still installed where no SSE could handle. It must also be seen from the side that needs to be to test the updates kept a corresponding hardware. MS does not have to pay attention to the updates for Windows XP Embedded or POSReady 2009 on hardware before 2009, so it is to be assumed that future updates, which we also use for Windows XP, will cause problems for older hardware. For me a more factual explanation for your problem with KB4343674 on your PIII.
2 -
1 hour ago, jbclem said:
Here's what's happened...I downloaded heinoganda's fix packages, but during the installation it turned out that I had to have a WinXP installation disk. Which I didn't have.
Which package was required for the installation media of Windows XP sp3? 1,2 or 3? If it was the second, the files can be found in the folder "%TEMP%\XPSETUP.TMP\I386". You may need to install the second package twice, reboot after the first time, and then again.
1 hour ago, jbclem said:I couldn't find anyway to uninstall heinoganda's fix, so I tried to run my ie6setup.exe which failed with the usual message about a newer version already installed.
Regularly IE6 is part of Windows XP sp3, it was restored with the first package of the folder "%windir%\ie8", of which in the folder "spuninst" spuninst.exe is executed. Meaning that the IE8 is uninstalled and the IE6 files and settings are restored (For me, the question is whether it has been tried to delete various files? Can the first package nor to possibly missing files to expand, you would have to tell me which you are missing. ).
I tested the packages myself in a regular Windows XP sp3 and POSReady 2009 and was able to install it back on IE6 and Outlook Express 6.
Regularly POSReady 2009 is delivered with IE7 and without Outlook Express 6.0 -
This is probably because MS various old processors (no SSE / old SSE version) in the updates no longer considered, this was communicated. I have tested Process Tamer (2.14.1.0) and Auslogics Disk Defrag (8.0.13.0) in my VM without problems. My Processor Core 2 Due 2.13 Ghz E6400.
1 -
The broken .NET Framework 2.0 sp2 update KB4338615 will be replaced by KB4344180. KB4338615 is no longer needed. The errors caused by KB4338615 no longer exist after installing KB4344180.
0 -
The parameter "/OVERWRITEOEM" is not required in the case of .NET Framework updates, superfluous and not intended!
Incidentally, if you install an update for Windows XP where this parameter is applied will suffice /o or -o.
0 -
That can not be meant seriously, the parameter "/OVERWRITEOEM" does not exist for updates from .NET Framework!
0 -
Under Windows XP, which can not compete with modern encryption technologies, Avast can only control what Windows XP supports for HTTPS connections, meaning that every HTTPS web page is blocked where it is not verifiable. For this reason, you should deactivate the HTTPS scanning function in the Web Protection component of Avast!
1 -
For user @jbclem I have created 3 packages for
1. the Internet Explorer 8 is uninstalled and the original IE6 files and settings are restored,
2. Outlook Express 6 and WAB installed and
3. a small update rollup where the required updates for IE6, OE6 and WAB installed.1
Windows cannot load the locally stored profile
in Windows XP
Posted
The last time it crashed my profile is a few years back. For me it always started with various error messages like Event ID Error 1517 and 1524 until the profile could not be loaded anymore. Since then, I have been using the User Profile Hive Cleanup Service v1.6g, where the functionality since Windows Vista is part of Windows and has not had any problems since then.