Cixert

I am looking for an antispyware type "adwcleaner", do you recommend any? I have downloaded Zemana which claims to be compatible with XP but it really doesn't seem to be. https://zemana.com/us/antimalware.html There is a list for Windows Vista, maybe for XP it will be similar

Hello, is there a list of updated antivirus and antispyware for XP?

I have again installed Windows Vista Enterprise and the result is the same. When I write "Bootrec /Fixboot" when starting the hard drive the BIOS shows the message "A disk read error occurred" + strang symbols. When executing third-party programs to modify partitions I see that the active partition C: FAT32 is not correctly recognized. These do not identify the format and name of the partition. This is only recognized by Acronis Disk Director and by Windows Disk Management, both from NT5 and NT6. This begins in sector 63. I have formatted this active partition in Fat32 again and manually copy the boot files: -From Windows XP ---> When restarting boot directly ntldr. -From Windows Vista ---> Don't let it format it. -From Windows Seven Console ---> When restarting boot directly Bootmgr. -From Eassos Disk Genius 5.4 ---> When restarting boot directly Bootmgr. -From Minitool Partition Wizard 7.8 ---> When restarting an intermittent cursor appears. Then I execute "Bootrec /Fixboot" and starts correctly Bootmgr. The same if I execute the command with the other options. -From Minitool Partition Wizard 11.6 ---> When restarting an intermittent cursor appears. Then I run "Bootrec /Fixboot" and returns the error "A disk read error occurred" + strang symbols. The partition is again defective. -From Minitool Partition Wizard 12.5 ---> When restarting an intermittent cursor appears. The same errors as in version 11.6 This application, Minitool Partition Wizard, has ceased to be useful in its last versions.

Writing /kernel=ntoskrnl.exe also begins Windows Vista from NTLDR to hal's error. As I see that there are no people interested in this issue I do not continue to experiment with NTLDR. I have restored the original files that I had replaced from Windows Vista and now I try to start this same Windows Vista from Bootmgr. The Bootmgr menu appears to choose an operating system, I choose Windows Vista and the result is that now it seems that the same HAL problem happens as when I tried to start from NTLDR. Now I try to repair the beginning of Windows Vista with the DVD. I introduce the commands: "Bootrec /Fixmb" (OK result) "Bootrec /Fixboot" (OK result) "Bootrec /RebuildBCD" (result no Windows facilities) When restarting the BIOS says: "A Disk Read Occurred Error" + Strange symbols. I repeat the commands and the result is the same. Automatic repair does not work either. Third parties programs do not find errors, repairing the MBR does not work, the hard drive and its partitions are accessible from XP. Chkdsk does not give error. I have the following on this hard drive: 1-FAT32 Active Partition with boot manager. 2-NTFS Windows Vista. 3-FAT32 Windows 2003. 4-FAT32 Data. Then I start the Windows Seven repair disk console and I introduce the "BOOTSECT /NT52 C:" (not available in Windows Vista). Now the BIOS boot the hard drive with boot.ini and Windows 2003 starts perfectly. I enter the command again: "Bootrec /Fixboot" And the result is again that the hard drive is not accessible from the BIOS. "A Disk Read Occurred Error" + Strange symbols. Then I introduce the "BOOTSECT /NT60 C:" command: " And now the Bootmgr menu to start Windows Vista reappears. I enter the command again: "Bootrec /Fixboot" And the result is again that the hard drive is not accessible from the BIOS "A Disk Read Occurred Error" + Strange symbols. My conclusions about the experiment to repair the start of Windows NT6 or higher is "impossible mission". Strange errors also happened to me when trying to repair Windows Seven. https://msfn.org/board/topic/184546-reov-boot-windows-lononghorn/?do=findcomment&comment=1242025 I will install Windows Vista again and I will enter the command again "Bootrec /Fixboot" To get out of doubt. In any case, the option to repair the start of Windows Vista has been from Seven's DVD "Bootsect /NT60 C:" and to exotate this this has been "Bootrec /Fixboot" from Vista's DVD.

Well, no problem. I have tried rebuild 8 and this works very well. I understand that all versions from Rebuild 7 are Ram-Friendly right? I have tried it in Intel Atom Notebook 2010 Year with 1 Gib Ram and in Pentium IV with 2 Gib Ram, now this work very well. At this time I do not find links to download any version. links are down?

Has anyone achieved it, is there any method? Experimentally I am trying to start Windows Vista 6.0.6000.16386 (Vista_RTM.061101-2205) Enterprise from NTLDR. I have managed to get hast here. Any tips to continue? Windows Lonchorn/Vista, at least between versions 6.0.5048 and 6.0.5112 install bootmgr, but are also boot from ntldr version 2005 (Required*). *Required NTLDR version 2005 (ntldr not OK version 2003 and not ok version 2008) I am using this ntldr version and I have modified boot.ini on 6.0.6000 multi(0)disk(0)rdisk(0)partition(3)\Windows="Windows Vista" /NOEXECUTE=OPTIN /FASTDETECT /ACPI /HAL=HALMACPI.DLL /KERNEL=WINLOGON.EXE But arriving at the point in the photo this gives the error "Load Needed Dlls for Hal" I have tried to replace the original HAL 6.0.6000 with the HAL of 6,0,5112 but there is no difference.

I have little knowledge about Windows NT6 start. This is evident. I am now obliged to use an application that is no longer compatible with XP by imposition of the Government of Spain (Autofirma 1.8) to be able to send official documents to the country's administration. Before using any superior version of Windows 2003 on my personal computer, the first thing I want to know is how they start. And not vice versa. Use these and these not start. Or what is worse, that the data of my main computer are erased. With all respect for who knows more, although some people have less knowledge can contribute a lot, if they work with collective intelligence. Well, all people have different points of view. I am now doing tests in Windows Seven. I have restored a backup copy of the starter boot. I try to repair the installation from the Windows Seven console on another computer. I have connected the hard disk by USB. I follow the official steps, but the installation is not repaired.

Some nuances about my previous comments. The versions that start Windows with Bootmgr+NTLDR are the Shorthorn versions "Based Longhorn" Since although the installer is Bootmgr these versions are really NTLDR. On the other hand, Longhorn Pre-Reset from 4000 to 4093 use a 32-bit installer but these are NTLDR and not Bootmgr implements. Longhorn Post Reset, at least between versions 5048 and 5112 install bootmgr, but are also starting from NTLDR version 2005 (required*). These versions boot from both methods but these only install bootmgr. The latest Longhorn version that can be installed in Fat32 is 5001. That is, it coincides with the last one that NTLDR has.

It is possible that when the text did not appear "press a key to start the CD" the BIOS boot priority changed without realizing it, but when the message did appear I confirm that CD start priorities in the BIOS were correct. The Windows NT 5 (2000-XP-2003) installation CD was not able to start, when it was frozen for some reason, not being capable of detecting the hard drive modified by Longhorn/Shorthorn before being able to start the file installation load. To work again it was not effective to erase the hard drive and partition again. The only solution was to convert the hard drive to GPT and covert it again to MBR. The NT6.x DVD, yes did start correctly with this same hard drive before performing the conversion operation. I continue to do tests: 1-I have installed Windows Seven on the Notebook computer. 2-I have installed Shorthorn on the computer desktop. My purpose is to try to start Windows Seven with the Windows Longhorn boot, copying Shorthorn files into Windows Seven. I still cannot comment conclusions, because in several tests the following has happened to me: -As deleting the boot files from the active partition all partitions disappear. That is, with the hard drive connected as an external USB to Windows XP. I delete the "Boot" folder and all partitions disappear. I have performed more tests and also happens when Bootmgr, Ntldr, Boot.ini, etc. erase at the same time. This has not happened when one by one erase. I have copy and paste other folders that have not boot files and the problem has not happened to me. I indicate that in certain circumstances Windows does not let these files erase, in others erases them without problems and in others the partitions disappear. Hard drive 4 partitions in Notebook computer: 1-Primary FAT32 Active partition with boot manager. 2-Primary NTFS Windows Seven. 3-Primary Fat32 Windows XP. 4-Primary FAT32 Data. From XP I install Windows seven in the second partition. I confirm that now the number 1 partition begins in sector 2048 (I don't know if before). Then I extract the hard drive and connect it to the computer, it is the external USB and I started Windows XP. I erase some start files and partitions disappear. This does not always happen. I don't know what depends. Then I have copy the original boot files of the Windows Seven and I have tried to repair the boot with the Windows Vista DVD. 1-I undo automatic recovery message Windows seven partition. 2-I execute the commands: Bootrec /Fixboot Bootrec /Fixmb The result is that Windows Seven not starts. Then I try to recover automatically, but the message repair Windows Seven now does not appear. However, Windows Vista DVD says trying to repair. The result is that not only does Windows Seven not start, but now the Windows Seven partition is in RAW and inaccessible. In addition the fourth partition appears inaccessible. I try to recover the partitions with Easeus Partition Master but the program does not finish progress and does not find the correct partitions. Then I again erase the Boot folder of the active partition and the partitions disappear again. Then, after disappearing again, Easeus Partition Master does find and recover the correct partitions. I am struck that this program also has the following MBR recovery options. -2000/XP/2003 -Vista/2008 -7/8/10/2012 Is the Vista MBR and Windows Seven different? I am investigating the initial sector by partitioning from the record administrator, it could be the following: Sector 63 -> Windows NT 5.x -> Align hard drives with 63 sectors per track (512 bytes per cluster). Sector 2048 -> Windows NT 6.0 -> Align hard drives with 4096 bytes by Cluster. Sector 4096 -> Windows NT 6.1 and Superior -> Optimizes alignment in hard discs 4096 bytes by Cluster. The Eassos Disk Manager program allows you to choose the initial alignment when partitions are created and also allows partitions to the initial sector 63 since 2048 or 4096. I do not extend anymore, this requires an integer post apart ... Ok, then I now try to recover the installation of Window Seven with Windows Seven DVD with the hard drive connected to the USB desktop. I can't repair Windows Seven installation. I execute: -Auto recovery = It has not been completed. -Console: Bootrec /Fixboot Bootrec /Fixmb Bootrec /rebuildbcd Bootsect /NT60 C: No option manages to repair the boot. With how easy it is to repair the NT 5.X boot it seems that NT 6.x boot resists me. I can't repair Windows Seven boot.

Several strange things have happened to me that I cannot solve after trying to install the versions of Shorthorn that were not allowed to be installed from XP, because they said "the files cannot be found in the temporary path". 1-I can not repair the bootloader of the hard drive in XP format. 2-On boot the NT 5.x installation CD does not get past the "press any key to start the CD" screen with this hard drive. 3-Finally the boot CD does not start (it does not show the message press a key to start from the CD either). I tried to install Shorthorn Main Development 3801 from CD on another computer with a hard drive with 4 FAT32 primary partitions. When I reboot the BIOS it does not find any operating system. I check that in the boot partition there is the bootmgr, ntldr and boot.ini file but there is no Boot folder. I try to repair the boot by starting the Windows 2003 CD with the fixboot and fixmbr commands but the hard drive won't boot. I copy ntldr, ntdetect.com and boot.ini from Windows XP to the boot partition and run fixboot and fixmbr again. But the hard drive still won't boot. I delete all partitions from Windows XP and recreate 4 primary partitions in NTFS from Minitool Partition Winzard. I reboot with the Windows 2003 installation CD in the CD drive and get the message "press any key to boot from CD". I press a key but the installation CD does not start. I try the Vista installation disk and it does start. I delete the partitions again with Easeus Partition Master and the CD does not start either, then with Eassos DiskGenius and the CD does not start either, then with Macrorit Partition Expert and then the message "press a key to start from CD" no longer appears. from any NT 5. If NT 6 CDs are booted. The problem only occurs with this SATA hard drive, after the operations performed. Edit: I have managed to solve the problem by converting the disk to GPT and then converting it back to MBR with Acronis Disk Director. So I have installed Shorthorn 3801 on a single NTFS partition. As a curiosity I comment that from this boot.ini I can start my other hard disk with w2000 and XP but from the boot.ini on the 2000/XP disk it does not start Shorthorn/Longhorn. Is there a way to boot windows vista from a boot.ini? It seems that this could be one way.

Caution only change the letter if the operating system previously used another letter. The letter change means that Windows does not find the paths of many files and does not work well. The drive letter is determined within the operating system registry. Part 1: Change the drive letter from the operating system itself: -Start+run+regedit -HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices -To change C: to D: \DosDevices\C: rename to \DosDevices\Z: \DosDevices\D: rename to \DosDevices\C: \DosDevices\Z: rename to \DosDevices\D: -Restart. Part 2: Changing the drive of one operating system from another operating system. Edit the registry remotely: -Start+Run+regedit -Select HKEY_LOCAL_MACHINE -Go to menu File+Load subtree -Find the SYSTEM file in the folder of the other operating system (on XP \WINDOWS\system32\config) -Load SYSTEM and choose any name. -Follow the steps indicated in part 1. -Select the loaded subtree. -Go to menu File+Download subtree.

I have tasted again with Windows Vista, I was wrong in some concepts @jaclaz The final test says: -Windows Vista RTM does not start with ntldr and boot.ini -Yes, any Windows Longhorn does, at least up to 5231, maybe Windows Vista can start with the Dual Longhorn charger (Bootmgr+NTLDR). -Windows Vista does not work in Fat32, I have achieved it almost install in Fat 32, cheating it. After the install menu "choose partition" I have formatted the partition of NTFS to Fat32 with Alt+Tab. Then look almost until the end. Just, at that final moment, this says "a critical component has not been installed, restart to repeat boot process" After restarting it says "missing bootmgr" despite being installed.

You commented on this in another thread. I don't remember the method I used to partition this hard drive. But I only use Windows 2000/XP and compatible programs. It is a mini notebook without CD ROM. I did it via external USB. Until now I was working with XP and I did not modify the partitions to install Longhorn, except to format the 2nd partition to NTFS and convert the 1st partition to NTFS from FAT32. On the 1st partition I don't install operating systems, I only have the boot files. I will try to see the MBR partition machine code, I remember some old tools. What I can contribute is that it is possible to fix Longhorn to only boot with ntldr by disposing of bootmgr with the Windows XP recovery console. And I seem to remember that I also did it in a test with Windows Vista RTM. I'm going to try Windows Seven now. Greetings

With i386 I mean that the installer is compatible with 386, it works at 16 bits. (the installer for the 16-bit versions includes the i386 folder and the 32-bit versions include the source and boot folders) I just verified that the Vista 6.0.5231 installer (the one used by Shorthorn) requires both bootmgr and ntldr (versions before 4000 only ntldr, 5000 and 5001 post reset only ntldr). It starts with bootmgr and the bootmgr menu appears but after choosing an OS it jumps to ntldr and boot.ini appears The system doesn't boot whether I delete bootmgr or ntldr. In addition, the version of ntldr is different from that of NT 5.1, the previous one is not compatible. Longhorn pre-reset versions (up to 4093) do not install on FAT32 but I just verified that this 5231 installer installs Windows on FAT32. What has surprised me, regarding your idea of not using the Windows Disk Manager, is that I have placed the hard disk in another computer and after running the Windows XP Disk Manager, all the disk partitions have disappeared, without performing operation. "Only booting Disk Manager" why? In addition, the same thing has happened with just starting Acronis Disk Director without performing any operation on the hard disk, why? I have recovered them with EaseUS Partition Master. Offtopic: For those who think of trying Longhorn and Shorthorn, it's not worth it, it's all problems and errors, nothing works and no support. In Shorthorn not even work 360 Extreme Explorer and neither@roytam1 browsers, except on Shorthorn 3706 -Longhorn based- and Shorthorn Main Develoment. Also I have tested One Core Api @Skulltrailon all Shorthorn versions besides Windows XP. Only it just got me installed on Shorthorn 3706 causing a lot of problems and no NT 6 compatible programs work. Blue screen is guaranteed in XP and the system is normally not recoverable. Great care. Shorthorn 3790 versions (Main Development) can not be installed from XP to another partition, so I have not been able to test.

Newer versions of Windows Longhorn do not use i386 but bootmgr. From what I remember reading, both Longhorn and Vista call ntldr and this version of ntldr checks to see if boot.ini exists or bootmgr exists with his boot folder. The problem happened in Shorthorn 4033. Now I have tried other versions and I have verified that the problem does not recur, it only happens in 4033. All Shornhorn versions -Longhorn based- use the installer of Windows Vista build 5231. But I had the question of how to repair the installation . I will try those third party tools. In the original Longhorn I have not had the problem, although I have not been able to complete any installation successfully due to different problems. Original Longhorn requires an NTFS partition to perform the installation.

I have tested all original Longhorns from a hard drive with 4 primary partitions. 1-Boot Files i386 boot.(boot partition). 2-Empty for the installation of the new system. 3-Windows XP x32 NT 5.1 4-Data I start the installation of the iso from Windows XP. No bootmgr based version has finished installing on my computer. I have tried the Shorthorn variant. This does install completely and the interface starts, but after the first reboot the message "ntldr is missing" appears. I have reviewed the files manually and they all seem correct. I have tried to recover the bootable boot from the Windows Vista recovery console command line but it does not recognize any Windows installation. The only way I've had to recover the boot has been from the Windows XP console with the "fixboot" command. Fortunately, the boot is recovered through boot.ini and Windows Longhorn star. How can you recover the original boot of Windows Longhorn? Preferably with command line or manually. I have not found any program that manages to recover the boot. EaseUS manages to recover MBR and partition table but does not fix boot. what does fixboot actually mean?

I have found a way to disable duplicate creation of 8.3 short names on FAT32 plus NTFS but this does not apply when it exceeds the 260 character path, in which case XP automatically renames long files to 8.3, when the folders are copied. This issue does not happen on Windows 2000. To disable: fsutil behavior query disable8dot3 1 To enable: fsutil behavior query disable8dot3 0 To check status: fsutil behavior query disable8dot3 https://learn.microsoft.com/en-us/windows-server/administration/windows-commands/fsutil-behavior On the other hand, I have read here that it is convenient to disable the function of creating duplicate names.I don't know if this can cause problems, for example with tools to recover the system that work from CD-ROM or floppy disk. https://ttcshelbyville.wordpress.com/2018/12/02/should-you-disable-8dot3-for-performance-and-security/ BEWARE the commands of the last link do not apply in XP. (not to be confused with the NT 6 fsutil 8dot3name command) I have found the following tools to detect long paths: -Long Path Tool (also copies long paths) (demo) -TLPD (Too Long Paths Detector) -Path Scanner (trial 13 uses) -Robocopy, command to copy folders from Windows Server 2003 Resource Kit Tools

Links are down...

So there seems to be life after death :-) I have not found technical information about it, but I will tell my experience. Today, using Windows 2000 with an NTFS external unit per USB I started decompressing about 10 very large files, between 0.5 and 10 gib. In parallel I have put a 50 gib file from the Internet. Then the system, at a given time, has shown me a blue screenshot. *** STOP: 0x000000d1 etc Driver_irql_not_less_or_equal And nothing more. It has surprised me that the memory dump message did not appear, or any other message. So, when I was going to press the restart button, I have noticed that the external hard drive had the writing light flashing. Thus, I have left it for an hour in this situation. Of course, disconnecting the Internet in case the 50 gib file continued. I really wanted to wait to see what happened when I finished blinking the light, to see if the system showed more messages on the blue screen, but I have not had patience. When I have returned, seeing it in the same situation, I have not been able to wait any longer and I have pressed the restart button. The fact is that at the beginning of Windows, no error was found on the hard drive and the 10 files in the process of decompression had been completed 8. Therefore, it is evident that the system continued working despite showing the blue screenshot and did not go to state "Requiescat in Pace".

I had been on a computer with Windows 2000 SP3 for years working with USB 1.1 until today I found the solution to enable USB 2.0 The original driver was an ICH7 with the USB EHCI service. This gave code 10 error, the device has not been able to start at the USB of the motherboard. I was thinking that may not work EHCI at W2000 SP3 and that I would have to update to SP4, but this has not been necessary. I have update usbhub20.sys to version 5.00.2195.6655. and it work. In the device administrator I have chosen the driver "Intel Pci to USB Enhanced Host Controller" Then a new driver category has appeared named "Standar USB Hub" and this has automatically installed the Driver "USB 2.0 Root Hub" working perfectly on my computer. I have the question of whether there is any performance difference with USB EHCI. I would also like to know where to find the EHCI service in Windows 2000, since in Services.msc it is not.

ok, I thought that the double name was only in NTFS, I read that in FAT too. The problem is that when I copy and paste a file into a long path, that it exceeds the character limit. Windows XP automatically renames a file with a long name to a file with 8 characters. If XP does not achieve 8 characters it gives an error, but if it can it automatic renames. This does not happen to me in windows 2000, it always gives a long path error. Does it only happen to me on XP? This has been happening to me since 2001. is it possible to recover in the File Allocation Table the original long file name? Both in the console and in Total Commander it shows the short name of the renamed file. The registry entries you comment are fine

This is a problem that I have had without a solution for a long time, I use FAT32. When I copy multiple folders if any file has a name that exceeds the Windows file length limit then XP copies it without giving any error and changing the long name to a short one with 8 characters and "~" symbol. For example, if the file has the name: "program to read documents PDF.exe" Windows XP renames it without giving any error to: "program~.exe" Apparently the file keeps its real name somewhere, since a shortcut still finds it with the short name, but it prevents me from knowing the true name of the file. I would like to know how: 1-Be able to see the long file name again. 2-What Windows XP gives an error message when I am copying a file with a long name that exceeds the limit, instead of automatically changing the name. I don't have this problem in Windows 2000, so when I go to copy and paste a lot of files I have to restart and use w2K, which gives me an error that it can't copy long names instead of renaming them.

It's me, @AstroSkipper @mina7601 In my profiles folder I see 5 profiles. The newest profile is "jvsrhsc8.default-default-3" But in the profiles.ini file I see a mix of profiles. Is it safe to delete all profiles and leave the newest one? what should the profiles.ini file look like? What does locked=1 & isrelative=1 mean? Thanks. [InstallB2BEF67B3394E6F3] Default=Profiles/5j62w0ky.default-default-1 Locked=1 [Profile3] Name=default-default-2 IsRelative=1 Path=Profiles/gtdvt7r6.default-default-2 [Profile2] Name=default-default-1 IsRelative=1 Path=Profiles/5j62w0ky.default-default-1 [InstallC48CA6CD8F76FD36] Default=Profiles/c3s58rv4.default-default Locked=1 [Profile1] Name=default IsRelative=1 Path=Profiles/6ay5acid.default Default=1 [Install77095BA9BFBDBF19] Default=Profiles/jvsrhsc8.default-default-3 Locked=1 [Profile0] Name=default-default IsRelative=1 Path=Profiles/c3s58rv4.default-default [General] StartWithLastProfile=1 Version=2 [Profile4] Name=default-default-3 IsRelative=1 Path=Profiles/jvsrhsc8.default-default-3 [Install85442B1DBF4D6613] Default=Profiles/gtdvt7r6.default-default-2 Locked=1

Fixed: It was a worm. I use Service Pack 3 with the Blaster, Sasser & Conficker update packs, but on both computers I had been messing around with changing the hal and because of this old copies version of the hal layers were restored. On the desktop computer I fixed it by restoring copies of ntldr, hal.dll BOOTVID.dll and especially ntkrnlpa.exe Interestingly on this computer it worked by restoring a previous version copy of the hal layer and connecting to the internet did not reproduce the problem again. At that time I still did not know the problem cause. In the laptop that did not work for years, after resetting the registry, it stopped booting only after connecting to the Internet. I've restored a registry copy, reinstalled the updates anti-blaster, Sasser... And the problem has not returned. It is curious that neither Avast nor Malware Bytes detected any virus in the scan performed. On the other hand, the registry change comparator files showed different results when comparing both registries. But on the laptop they showed 2 very suspicious keys with FAT32 format. HKLM\SOFTWARE\Microsoft\Cryptography\RNG\Seed: AB 3C CD E7 5A 38 7D 97 07 0C F0 9F E6 6A B2 3F E8 EC 7F 61 06 98 D2 2E FA 3D 1A A4 52 54 40 7C 1F 43 E2 7A 9C 02 94 13 C8 64 9F D8 F8 20 19 35 50 A2 F4 6A DC 06 95 6A 1F A2 0E 1C 2F 53 1C F1 01 28 52 81 A7 51 39 91 A4 9A 85 06 2C B3 84 E9 HKLM\SOFTWARE\Microsoft\Cryptography\RNG\Seed: 97 93 BC 79 5D DE C2 4F C3 E9 0B AF F8 A7 90 B7 9D 16 EF E8 C0 F6 EB C1 8A 58 45 6A D6 B4 73 E2 03 9E B8 BB 75 50 4A 9F 28 9D B0 07 AE 64 6A 20 07 4B BB 13 20 F9 C0 F6 1D C7 DE 6D 94 7B A0 FC 12 EC 4D E0 BC 52 D8 00 1C 93 5E 0A 85 67 D6 74 edit For the exposed: -Desktop computer ---> The problem arises with or without an Internet connection. Fixed restoring ntkrnlpa.exe previous version -Laptop ---> The problem occurs only when the system is connected to the Internet. Fixed updating ntkrnlpa.exe After writing the previous lines I have gone to upgrade Windows 2000 on both computers with: -KB824146-x86 Anti-Blaster -KB835732-x86 Anti-Sasser -KB828741-x86 Anti-attack by RPCSS On the laptop I haven't had any problems, but on the desktop the problem returned after installing KB824146-x86 Anti-Blaster and restarting the system. I haven't checked if it updates ntkrnlpa.exe Then I went to install KB835732-x86 Anti-Sasser, but it gave me the error "The installation program could not verify the integrity of the Update.inf file" In Internet forums it says that it is because the encryption service is not running. I do not see this service installed in Windows 2000. It is possible that I have uninstalled it in the past. The problem has been solved by restoring a fairly old version of the registry, from 18 months ago, on which I have been able to install the updates.

sorry, the post was originally written in english from the computer. But I have gone to edit the post from the phone and when I hit send it has been automatically translated from English to Spanish. There is a problem with Chromium's automatic translators on smartphones and non-native language forums. I wanted to add that I have checked the Windows 2000 startup files, before loading SYSTEM. I am surprised that the file kdcom.dll says to load at startup without errors but this file does not exist in the Windows 2000 directory