If the msi file does not load what to do. Why is the slider not moving in MSI Afterburner

After installation MSI Afterburner, users often observe that the sliders, which in theory should move, are at minimum or maximum values and it is impossible to move them. This is perhaps the most common problem with this software. Let's figure out why the sliders are not moving in MSI Afterburner?

After installation MSI programs Afterburner, this slider is always disabled. This is done for security reasons. In order to fix the problem, go to "Settings-Basic" and put a tick in front of Unblock Voltage... When you click "OK", the program will be restarted with user consent to make changes.

Video card drivers

If the problem persists, then you can experiment with the video adapter drivers. It happens that the program does not work correctly with outdated versions. In some cases, new drivers may not be suitable. You can view and change them by going to "Control Panel-Task Manager".

The sliders are at their maximum and do not move.

In this case, you can try to fix the problem through the configuration file. To begin with, we determine where we have the folder of our program. You can right-click on the shortcut and see the location. Then we open "MSI Afterburner.cnf" using notepad. Finding a record "EnableUnofficialOverclocking = 0", and change the value «0» on the "one"... To perform this action, you must have administrator rights.

Then we restart the program and check.

Sliders are at minimum and do not move

Go to "Settings-Basic"... At the bottom we put a mark in the box "Unofficial overclocking"... The program will warn that manufacturers are not responsible for the consequences of changes in the card parameters. After restarting the program, the sliders should be active.

The Power Limit and Temp sliders are not active. Limit

These sliders are often inactive. If you tried all the options and nothing helped, then this technology is simply not supported by your video adapter.

The video card is not supported by the program

MSI Afterburner is designed for overclocking cards only AMD and NVIDIA... There is no point in trying to overclock others, the program simply won't see them.

It happens that the cards are partially supported, that is, not all functions are available. It all depends on the technology of each specific product.

Introduction

Our installers for Windows contain a complete client-side installer (MSI) package (built on top of Windows Installer v2.0). The network installation instructions assume that the user is familiar with the basics of Windows Installer, specifically deploying MSI files. This package can be used with any Windows operating system that supports Windows Installer v2.0.

Installation on a network server

  1. Double click on the resulting file ( Yenka_Setup_ (MSI) .exe)
  2. Install this package to the shared folder for your programs.
  3. Attention : The program must be activated BEFORE deploying the package on the network. To do this, run "Yenka.exe" from the folder where you installed the program (<путь установки>\ program files \ Yenka \ Software \ Yenka.exe), and follow the activation instructions.

Installation

Installing an MSI package using the command line

  1. In the command box, enter the line:
    msiexec / i "<путь к MSI файлу>\ YK.msi "
    where:<путь к MSI файлу>this is the file path Windows package Installer. For example, a line might look like this: msiexec / i "C: \ Program Files \ Yenka \ YK.msi"
  2. Press the ENTER key
    Attention: Windows Service Installer will allow you to install in "stealth" mode using the "/ q" switch. For example: msiexec / i "C: \ Program Files \ Yenka \ YK.msi" / q... To show the progress bar of the installation, you can use the " / qb".

Removing an MSI package using the command line

  1. From the "Start" menu, select the "Run ..."
  2. In the command box, enter the line:
    msiexec / x "<путь к MSI файлу>\ YK.msi "
    where:<путь к MSI файлу>this is the path to the Windows Installer package file
  3. Press the ENTER key

Errors when installing applications from files with the .msi extension are one of the manifestations of problems with the Windows Installer service (in the Russian version, Windows Installer). Users of all versions of this OS, with the exception of the earliest, are faced with a similar phenomenon. Until now, the problem with the installer is one of the common reasons why users decide to reinstall the system. Let's try to figure out how to avoid this. The reason why Windows Installer is not working may be the following:

  • viral infection, and removing the virus does not always solve the problem;
  • incorrect installation Windows updates;
  • malfunction of security software, when instead of blocking one suspicious msi file, the installation service is blocked entirely;
  • changes in security policies on the computer;
  • damage system files or registry for reasons not related to viruses (removal of installer components, unskilled editing of the registry, "crooked" software, malfunction hard disk etc.).

Checking the integrity of the Windows Installer structure

Windows Installer is represented by the following components:
  • file C: \ Windows \ System32 \ Msiexec.exe - directly by the installer application itself;
  • the file C: \ Windows \ System32 \ msi.dll - the Windows Installer library;
  • by the Msiserver service, whose settings are stored in a registry key.
Before diagnostics, it is important to make sure that both of these files are present in the system, that the above section is in the registry and its parameters have normal values ​​(the values ​​can be viewed in the registry of a similar, workable system). Also open the list of services (press Windows + R and enter the command services.msc in the "Open" line of the "Run" application). Search for "Windows Installer" and make sure it starts. If there are no files, copy them from another system of the same version or from the installation disc. If the registry key is missing or damaged, transfer it from the production system as well. To do this, on a working computer, start the registry editor (C: \ Windows \ Regedt.exe) and find the above-named section. Expand the context menu of the msiserver folder by right-clicking and click the "Export" item. Save the file in .reg format and transfer it to the problem machine. Double-click this file and confirm your consent to add data to the registry. Reboot your computer. If the Msiserver service still won't start, check if the RPC (Remote Procedure Call) service it depends on is running. You can re-register the installer files and restart the service using the set special teams, on the command line. For convenience, you can create a batch file: paste the set of actions into notepad and save as with the .bat extension. To run the file, just double click on it. To make the changes take effect, click on the desktop and press F5.

Checking security settings and access rights

Windows Installer may not work also due to the fact that it is blocked by security software or operating system no required rights. First, let's figure out the software. If you have an antivirus installed, temporarily disable it. Each product has its own disabling methods, but most often this is done through the context menu of the antivirus icon in the system tray. Now let's get into the rights. Open the context menu of Msiexec.exe and expand its properties. Look at the list of groups and users on the Security tab. Among them must be "System" and the service "Trustedinstaller", and the latter must have full access to the file and be its owner. The system must have "read" and "read and execute" permissions. The Trustedinstaller service first appeared in Windows Vista, so in Windows XP, you must give the system full access. Everything written below applies to versions released after XP. To check who the owner of Msiexec.exe is, click the Advanced button on the same tab. In the next window, expand the "Owner" tab. Take ownership of the Trustedinstaller service if specified otherwise. If it's not in the Change Owner To list, click the Change button followed by Other Users and Groups. Enter Trustedinstaller in the "Enter names ..." field, click "Check Names" and OK. Return to the previous window. On the Effective Permissions tab, assign the required rights to the Trustedinstaller and the system. The msi.dll library should have exactly the same security settings. Now let's check if there are any restrictions for the "System" user to access the following:
  • system drive (usually drive C);
  • temporary folders (these are C: \ Windows \ Temp and C: \ Users \ Current_user \ AppData \ Temp);
  • folder C: \ Config.Msi;
  • the folder where the msi file from which you are trying to install the program is located.
The system must be given full access to all these objects. This is done in the same way as we discussed above. After these operations, in most cases, the problem with the installer is successfully resolved. If our advice did not help you, the cause of the failure lies in something else and specialists should already deal with it.

Windows installer error is one of the most common pop-up problems encountered by operating system users. Windows systems.

The error can appear regardless of your OS version.

Reasons for the error

You can scan the OS using the Sfc / scannow command. You need to enter it in the command line window.

Run command line can also be done in two other ways:

  • Start -> All Programs -> Accessories -> Command Prompt.
  • Start -> Run and enter the program name cmd.exe

In a few minutes, you will be provided with detailed information about OS disks, corrupted files, problems with services and other system programs.

The command line will not only find damaged and damaged files, but also replace them with workable ones.

After scanning, close Command Prompt and reboot your Personal Computer or laptop. Try running the installation process of any executable file.

Also, Microsoft offers users automatic utility, which is able to solve the problem of the installer.

Go to the official website of the company https://support.microsoft.com/en-us/mats/program_install_and_uninstall

In the window that opens, click on the "Run now" button. The utility will restore the correct configuration of the installer.

It should be noted that the utility does not work with the eighth version of the operating system.

Configuring installer access to msi files

An installation problem may be caused by the installer not having access to the .msi files. The user can solve this problem on his own.

Follow the instructions below:

  • Find your installation file and right-click on it;
  • Select the properties window;
  • Go to the security settings tab;
  • In the group or user text box, check if there is a user named "system". If it is not there, you need to add the user manually;

  • To add a new user, click on the Edit button and then on the Add button;
  • In the text box for the name of the object to select, write the word "system" (without the quotes). If you are using English version operating system, enter the word System;
  • The entered word should instantly become underlined, as shown in the figure below;

  • Check the box for full access and now click on the OK button;

The installer will now be able to access the executable file. The installation should complete without problems.

Note that in some cases, block access to installation file can antivirus software.

To solve this problem, you need to go to the operating system under account administrator, turn off the antivirus and enable compatibility with other OS versions in the antivirus properties settings, as shown in the figure below.

Windows Installer Error - Solutions

A fairly common problem among users of the Windows operating system of any version - msi error when installing programs from a file with the .msi extension. In this article, I will describe common problems with the Windows 7/10 / XP installer and options for solving them, as well as make a video on the current issue.

Files with the .msi extension are the usual installation packages (distributions) from which the program is installed. Unlike the usual "setup.exe", to run the file msi system uses the Windows Installer service (msiexec.exe process). Speaking in simple words, Windows Installer will unzip and run the files from the distribution. When Windows Installer doesn't work, various errors appear.

In general, it pisses me off terribly, tk. after a stupid error message, it is completely unclear what to do next. Microsoft has specially designed the Windows Installer to expand the installation of programs (this mainly concerns system administrators), but did not take proper care of the bug-free operation of this service, or even adequate reporting of problems. And now we have to rake it 🙂

Problems may be with the operation of the service itself or may arise during the installation of programs, when everything is configured, in principle, correctly. In the first case, you need to pick the installer service, and in the second, solve the problem with a specific file. Let's consider both options, but first the second.

Msi file errors

Very often errors appear due to insufficient system rights to files or folders. This is not to say that Windows Installer does not work, in this case, you just need to add the necessary rights and everything will work. Just yesterday I was faced with the fact that the downloaded .msi distribution did not want to be installed, while the installation wizard starts successfully, the parameters are selected, but then the system thinks for a few seconds and gives an error:

"Error reading from file" filename "verify that the file exists and that you can access it" (Error 1305). Translated "Error reading from file ... check if the file exists and if you have access to it." Well, isn't he stupid? Naturally, the "Retry" button does not help, and canceling terminates the entire installation. The message also does not carry a special semantic load, since the file definitely exists and I have access to it, otherwise I would simply not be able to run it and receive this message, besides, for some reason, in English 🙂

And the error is that it is not I who should have access to the file, but the Windows installer, or rather the System itself. The solution is very simple:

Now the installer error will not appear! You can add access to the entire folder from which you usually install programs, for example, to the Downloads folder, like mine. We watch a video on solving problems with access rights:

In Windows XP, the Security tab will not appear if the simple general access to files. To turn it off, you need to go to "Start -> Control Panel -> Folder Options -> View" and turn off the "Use simple file sharing" option. In the stripped-down versions of Windows 7/10 and XP, the Security tab does not exist at all. To see it, you need to log into it as an administrator.

More ways to solve the problem


The described method will help with different messages, with different numbers. For example, you can see errors like these in msi files:

  • Error 1723
  • Internal Error 2203
  • System error 2147287035
  • Error "This installation package cannot be opened"
  • Error 1603: A fatal error occurred during installation

In all these cases, setting the rights to the file and / or to some system folders... Check if the "system" has access to the temporary files folder (you may receive the error "The system cannot open the specified device or file"). For this:

After pressing "Enter" the path will be converted to "normal" and you will move to the real temporary folder. The rights to it should be checked. I also recommend that you clear the temporary folders from everything that has accumulated there, or even better, delete them and create new ones with the same names. If you can't delete a folder, read it, but it's not necessary.

If windows service Installer still does not want to work, then check the rights to the folder "C: \ Config.Msi", here the "system" must also have full access. In this case, you might have seen the "Error 1310" error. Just in case, make sure that you also have all rights to the folder WHERE you install the software.

Registry settings and services

The next way to fix the error is to restore the operating parameters in the Windows Installer registry.

To do this, download the archive and run two reg-files from there, according to your Windows versions... Agree to import settings.

Important! Front last action desirable! If the method doesn't work or gets worse, you can recover to your previous state.

On Windows XP or Windows Server 2000 install latest version installer 4.5.

If it doesn't help, then do another re-registration of the components:

  1. Press "Win + R" and enter " cmd ". Then, in a black window, enter the following commands in sequence:
    MSIExec / unregister
    MSIExec / regserver
  2. In response, there should be emptiness, no mistakes. If the problem persists, enter another command
    regsvr32 msi.dll
  3. Close the black window

If he writes that there are not enough rights, then you need to run.

If the commands were executed, but did not help, then run msi_error.bat from the archive, check the result.

The last option is to download the Kerish Doctor program, there is a function for fixing the work of the installer service and many others frequent problems Windows.

Also, many programs use the .NET Framework, so it won't be superfluous to install the latest version of this package. And, finally, one more piece of advice: if the path to the distribution file contains at least one folder with a space at the beginning of the name, then remove the space. Such a simple trick will solve your problem 🙂

Summarizing

Errors with the Windows Installer are very unpleasant, there are a lot of them and it is not immediately clear where to dig. One thing is clear - the system has failed and you need to restore it to a working state. Sometimes nothing helps and you have to. However, take your time to do this, try asking for help on this forum. Describe your problem exactly, tell us what you have already done, what messages you received, and, perhaps, they will help you! After all, the world is not without kind people 🙂