Error "inf-file txtsetup.sif corrupted or missing": how to fix?

With the error "INF file txtsetup.sif is corrupt or missing" basically only those users who try to install the version of Windows XP from a removable USB device (flash drive) are encountered. In this case, this problem is typical only for cases when the UltraISO program was used to record the installation distribution on the media. Next we will show how to bypass this failure in several simple ways. But to begin with it is necessary to understand the essence of the matter.

The txtsetup.sif INF file is corrupt or missing (state 18): what's the problem?

As it turns out, the whole focus is precisely in the program of transferring the distribution from the original disk or its copy stored on the hard disk to an external USB-drive.

The UltraISO application, although it is not advertised, has a number of limitations on this matter. Whether the program itself considers the modification of XP obsolete or irrelevant, or something else. But the most interesting thing is that the images of Windows 7 and above, written with this utility, do not cause problems, and the error "txtsetup.sif's INF file is corrupted or missing" does not appear ever. To correct the situation, you can offer a few simple techniques.

The txtsetup.sif INF file is corrupt or missing: what should I do in the simplest case?

As it is already clear, the first thing that comes to mind is to refuse to use the UltraISO program to create an image.

But if the user for some reason does not have another utility, you can also use it, although you will have to dig a little in the installation distribution itself (if you want everything to work).

Actions with installation folders

First of all, copy the original txtsetup.sif from the i386 directory of the main distribution directory to the root of the USB drive. Naturally, as the source should use the original DVD or downloaded from the official resource image of the system. In no case is it recommended to perform such actions in terms of images or distributions, in the general case called Re-Pack. The effect can not be achieved (sometimes you can get even the opposite action when the installation becomes impossible at all).

After that, in order to avoid the failure of the "INF file txtsetup.sif corrupted or missing" you need to rename the directory you want, assigning it the name $ WIN_NT $. ~ BT, then repeat the installation. Many, however, consider this technique too primitive and not giving the proper effect.

What should I do if USB media is not detected?

Sometimes the problem with the appearance of the error "txtsetup.sif's INF file is corrupt or missing" can also be related to the fact that the USB drive in the system seems to be there, but at the initial stage of loading it fails.

In the case of installing the system with a USB flash drive, even the presence of installed drivers does not guarantee that it will be possible to boot from it, although in normal mode the device is detected without problems.

The medium needs to be inserted into the corresponding port before the desktop or notebook computer is turned on and only then set the boot priorities in the BIOS settings (usually the Boot partition). If this did not work, you will have to completely reinstall the device drivers, even if the system recognizes this device under normal boot.

Creating Bootable Media: Some Nuances

However, since the problem is exactly UltraISO, which causes the error "txtsetup.sif's INF file is corrupted or absent", you should use programs like Win SetupFromUsb or WinToFlash.

Both programs are quite simple, but it's better to use the second utility. The fact is that it does not require the use of an image, but is capable of adding files and folders directly during recording. To do this, simply run the "Migration Wizard" and follow its instructions. During the creation of the boot distribution you will only need to specify the path to the full directory with the installation files and wait until the process of writing to the media has finished.

During installation, the system will display a window with several lines, but on the first start, select item 1 with the active line 1-st text mode setup (Debug boot rDisk 1 indicating partition 2 partitioning). If in the future an error regarding the HAL.dll library is issued, the installation should be repeated, but the fourth item (rDisk2 with partition 1) should be selected from the menu.

When the XP installation finishes, you will need to open the boot.ini file in any text editor and add it to the line containing the parameters "partition (1) = \ Windows" with the current version, via the right slash (/) with noexecute and then Shown in the image above.

By the way, the appearance of errors related to the HAL component is possible in the working system. Eliminating them is quite an easy task, although you can sort it out. True, in this case, it is this library that has to do with the main issue, so to speak, insofar as, however, to dismiss the emergence of such situations is not worth it.

As practice shows, this method works almost always. But this applies only to official distributions. If a user has a re-pack, created by someone unknown and out of what, such actions with all the will of the effect may not give. In addition, when downloading them, no one is immune from the penetration of viruses or malicious codes into the system (they can work even during installation, by inserting into RAM or starting with the startup processes). The cleaning process can be quite complex, and in some cases you will even have to use specific utilities such as Rescue Disk, which are loaded from removable media before the system starts and identify threats that the average user does not even suspect.

conclusions

This is the nature of the error "The txtsetup.sif INF file is corrupt or missing." How to fix the situation, it seems, is already clear. The technique of creating bootable media based on a program other than UltraISO, of course, looks somewhat complicated. Nevertheless, the problem can be solved in this way in 99 percent of cases out of 100. As for the UltraISO utility, its use is advisable only when creating images of other systems. Windows 10, for example, with a flash drive installed without problems. And the very nature of the issue is, apparently, not only in the above utility, but also in the Windows XP distribution itself, which can not always be used for installation in modern computer systems based on the latest configurations, which, incidentally, also relate to this software , To put it mildly, with complete disregard. If you try to install XP in its normal form, it's better to install the minimum package downloaded from the official Microsoft website, and then install additional service packs, including SP3, in turn and enable automatic updates in the system itself. At least, this will save the user from a permanent installation of the security update (and these products are designed exactly for this). But in general, and it's still far from the fact that the system will be installed in normal mode. Generally, although it is believed that XP seems to be one of the most simple and resource-less systems, alas, it can find so many bugs and shortcomings that you simply marvel at it. Therefore, it remains to advise users of any level of this modification not to use (especially since recently it was announced about the official termination of support for XP and Vista). So, think for yourself.