Windows does not load on msi. MSI laptop does not turn on how to start the wizard will prompt

i basically need help figuring out how to get Ubuntu 16.10 on amd64 (Linux 4.8.0-22-generic kernel) to boot successfully, so I can go back to actually use it. Downloading 16.04 LTS is also an acceptable solution.

below you will find spare parts with additional information about the system that I tried and I got the results. Thanks in advance for any help you can provide. Details ahead: oh!

summary

i bought this MSI laptop this July and after a lot of problems I was able to install Ubuntu 16.04 LTS for amd64 on it and use it for the last few months without any problem. (I have it as a dual boot system with Windows 10 on the other side.)

i upgraded from 16.04 -\u003e 16.10 a few days ago and I can't get the laptop to download anymore. Worse, I can't even get it to boot the same 16.04 LC I originally had from a Live USB stick. (For Windows it still boots, though.) The solutions I implemented the first time (see below) lot makes a difference this time around and I have no idea why this is suddenly the case.

please note that the update process appeared to complete it normally. I looked at a few similar questions here for a previous version of Ubuntu (e.g. 14.04), but they didn't work or don't apply to my situation. I've spent a few days on this already ...

Current behavior and error messages

it depends on which download option I choose, but here's the rundown of trying to download the current updated 16.10 installation (download commands included):

the basic commands are [F4], so I will only list the differences between the options for readability.

default boot: commands as shown above (with full uuid of course). The system freezes immediately after showing the Ubuntu logo. Bumped the key to show the console before hanging it shows that there are no messages ever written for it. Pre-update command Boot: Added [f5] arguments. Same behavior as above, these arguments were part of the solution to get it working back in July with 16.04 install. Recovery mode 1: This adds [f6] kernel arguments to many output showing services the start of the last message is [f7] (ie [f8] service) the screen is now black and no longer responds. Only the error message below is displayed. Recovery 2.recovery with the same arguments as # 3, but with and manually added, in principle, the result is the same as # 3

the only error I see went into options 3 and 4:

the download process doesn't hang on to this error. The boot process continues until the end of the lightdm service has started but has not yet been seen by the barker.

also, I would like to try the command [f10], but:

default boot option: commands as shown above (with full uuid of course). The system freezes immediately after showing the Ubuntu logo. Bumped the key to show the console before hanging it shows that there are no messages ever written for it. I actually removed the driver / package during a previous restore attempt ([f12]) in favor of a newer version from the official page. in any case, even if the driver had problems (for example, could not be loaded as LMB), I would (in most) wait for an invitation and a graphical user interface not show up, in this case, I have a terminal to log in and solve it. However, I can't get that far. [! D41 driver] before troubleshooting attempts and results [! D43 see]

since i have seen (and solved) some of these errors before i spent the last few days trying to go through the steps and resolve the issue before posting here. Unfortunately, things that worked before for similar problems (as far as I know) don't help.

initially successful solution (doesn't work this time)

when I didn't troubleshooted back in July, these are the things I did that helped me fix the boot and login issues I have:

[and D40] I actually removed the driver / package during a previous restore attempt ([f12]) in favor of a newer version from the official page. [! and D40] before updating the Boot command: Added [f5] arguments. Same behavior as above, these arguments were part of the solution to get it working back in July with 16.04 install. just like above, these arguments were part of the solution to get it working back in July with 16.04 install.

i tried these things this time for my 16.10 re-install, but I didn't see the same results. The secret is that I can't even do the 16.04 which worked in July to behave the same now as it did then. I have no explanation for this.

i also used [f15] on a previous laptop to work around the problem, but that with MSI I have nowhere.

Booting from USB with not [! D63, like] right now, trying to boot 16.04 LTS or 16.10 from Live USB, with default parameters1, the following message hangs in the console: [! D64 c] [F2]

Adding [f16] to the USB straight to the command produces slightly different output, with an erroneous line about

i've seen soft blocking messages before (in HP laptops) and I can always track them back to W-d and the CPU virtualization options be disabled in the BIOS and giving them a quick fix. While I don't immediately remember if I had these CPUs in tents back in July, if I did then I would tackle them in the same way. (You still need virtualization if you want to run virtual machines anyway, for example.)

corresponding BIOS settings

here are the parameters that were relevant before, in the section, and their not values \u200b\u200bthat worked before 16.04 -\u003e 16.10 updates. Please note that I have tried various combinations, enabling / disabling some of the options (for example, disabling multithreading, from state, etc.) without success. [! Tab d74]

additionally

disable secure boot to allow login after driver installation just like above, these reasons were part of the solution to get it working back in July with 16.04 install. switched on recovery mode 1: This adds [f6] kernel arguments to many output showing service start of last message is [f7] (ie, [f8] service) screen turns black and no longer responds. Only the error message below is displayed. recovery mode 1: switched on

the "Boot" tab

[stills taken with D80] before updating the Boot command: enabled [! frames captured by D80] boot mode select: with UEFI tab -\u003e

security safe loading menu

select boot mode: with UEFI recovery mode 1: switched on

Services may be needed

The operating system on MSI computer does not load, the computer turns on, there is a noise, but the operating system does not boot.

Why won't Windows boot?

There are many reasons why the operating system on MSI computer will not boot, and this is one of the most common reasons why users go to service centers. It could be a virus, of course, and it must be found and neutralized. Unfortunately, viruses are more technologically advanced than antivirus programs and are fairly easy to catch. The malfunction may be in the memory module, and if any errors are displayed on the screen, it is most likely that this is the case. The problem can arise due to problems with bridges, north or south, as well as with hard disk malfunctions. Of course, diagnostics are needed to determine what exactly the problem is. And, if it was not possible to determine the problem yourself, please contact our service center for repairing MSI computers and our specialists will identify the problem and fix it on a computer of any MSI model range.

Help is needed?

Contact us - we will help!

Fair prices

We agree on the cost of repairs before starting work and do not confront the fact of payment

Official guarantee

We support warranty service and give warranty up to 12 months

Free visit of the master

Some services our masters can provide on the road home or in the office

Original accessories

We work with official suppliers and do not mark up spare parts

A fairly common problem among users of the Windows operating system of any version is an 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", the system uses the Windows Installer service (msiexec.exe process) to run the msi file. In simple terms, Windows Installer will unzip and run 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's completely unclear what to do next. Microsoft specifically designed the Windows Installer to extend the installation of programs (mainly for system administrators), but did not properly take care of the smooth 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 successfully starts, 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 Simple File Sharing is enabled. To turn it off, you need to go to "Start -\u003e Control Panel -\u003e Folder Options -\u003e View" and turn off the "Use simple file sharing" option. In the stripped-down versions of Windows 7/10 and XP, there is no Security tab 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 may 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 should help. 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 the Windows Installer service still does not want to work, then check the folder permissions "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, corresponding to your version of Windows. Agree to import settings.

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

On Windows XP or Windows Server 2000, install the latest 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. There should be emptiness in response, 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 Kerish Doctor, which has a function to fix the installer service and many other common Windows problems.

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 tip: 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. This simple trick will solve your problem 🙂

Summarizing

Errors with 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 🙂

Does the BIOS boot up first after turning on MSI laptop? And then loading the operating system itself. If your MSI laptop does not boot, first you need to determine at what stage your system freezes or fails to start. The fact is that the BIOS is loaded with the motherboard and is the basic program for starting the entire system and remotely loading the operating system. Which can be located both on a hard drive and on external media. Black screen on MSI laptop and white letters - informs you about errors.

Errors on MSI laptop during system boot (white writing on black screen):

  • "DISK BOOT FAILURE, INSERT SYSTEM DISK AND PRESS ENTER"- the boot disk is corrupted;
  • "Boot Device Not Found" or " No boot device found"- no boot disk found - MSI laptop hard disk replacement or BIOS setup is required;
  • "BOOTMGR is missing Press Ctrl Alt Del to restart"- system boot error - Windows will need to be restored on the MSI laptop;
  • "a disk read error occurred"- disk reading error - MSI laptop hard disk needs to be replaced with a new one;
  • "reboot and select proper boot device and press a key"- reboot and select the boot device and press any key, there may be a problem with the hard drive, system or BIOS setup.

If the failure occurs at the time of loading the BIOS, then the matter is either:

  • Incorrect Bios settings;
  • Motherboard faults - MSI laptop motherboard repair is required.

In the first case, you need to either find an error in the BIOS settings, or reset all settings to factory defaults; in the second, step-by-step diagnostics of the motherboard itself is required, and the identification of the faulty element.
In case of "system startup failure" errors, the main problems are:

  • There is no connection between the hard drive and the motherboard. (breakdown, malfunctioning of the hard drive - replacement of the laptop hard drive is required)
  • Infection of the system with viruses that interfere with the loading of the operating system - it is required to clean the MSI laptop from viruses.
  • Malfunction of the algorithms of the operating system itself - reinstalling Windows on the MSI laptop.