Intelide

[Nayra Waddles]

IfWindows is unable to run application due to intelide.sys error or intelide.sys not found, intelide.sys may be missing or you may have a registry error. We strongly recommend that you download the latest official drivers, fix driver problems and keep them updated.

So close! I'm in the same boat as Valeriy: HKEY_LOCAL_MACHINE\asdf\ControlSet1\Services\intelide was set to '0'.

1. Is there any point to changing it back to '3' and then resetting to '0'?

2. If the setting was originally '0' does that indicate another problem?

Valeriy & Jeff... My instructions are for a VM with an virtual IDE controller. If you are using a virtual SCSI controller, you'll need to find out which driver it is that you need to change to '0'. It won't be intelide.

Awesome. I just used this tip to fix a physical machine Windows Server 2008 R2 that I converted to hyper-V using Acronis. One item: unload hive was disabled so I could not perform this step but the reboot worked anyway.

Thanks.

IF this does not work, and you are using virtual box, simply edit the settings and remove the virtual drive from the sata controller and add it to the ide controller. Virtual box adds virtual disks to the sata controller by default. Worked for me!

MANY THANKS :)

This worked for me, in Oracle Virtualbox set the controller type to LSI_SAS then just changed the start variable from 3 to 0 for the LSI_SAS service. Winner, much appreciated.

How this is not the #1 answer for Virtualbox 7B errors I have no idea. It's very technical, so maybe side-loading the registry is too scary for some people. But after 16 hours of trial and error with everything else under the sun, I found this site and had my Windows 7 VM running in about 30 minutes!!! Thank you SO much!

I had exactly this problem trying to get a P2V Windows 7 install up that I no longer had access to the Physical Disks, just the vhd created from disk2vhd ages ago. I knew the likely problem and was just searching the net for the process that you so kindly detailed. Thanks Dude!

From just another thirty-something fiscally conservative yet socially liberal married suburbanite with 2 young kids, 2 dogs, an hour commute, and bunch of nerdy hobbies. (There are likely more of us than we realise)

First comment of 2016 and this is still the best solution I have found.

Absolutely fantastic!! I tried the intelide setting and it didn't work, then I went through the whole list. It tuns out atapi = 0 went ahead and let Windows boot up. It took a few moments but the fact that it didn't immediately BSOD and reboot I waited patiently and.....the Angels sang in 2016 bruh!

(Windows 7 x64 laptop, AHCI boot, converted to VM used on Gen1 Hyper-V Windows 8.1 [will be transferring to a sever later today]).

Thank you soooo much.

March 6, 2016. Still valid.

Performing a restore from a backup of a physical machine to a VMware virtual. After successful restore, VM would BSOD. Followed your guide and had to change LSI SAS from 3 to 0 and the restored VM powered on and is running!

Awesome work!!!! This is always an issue for me going from P2V. I set the start value to zero for a number of values and it finally worked. Is there a way to definitively know exactly which driver/controller is the issue (in advance or afterwards? I remember using sysprep before, vbs based system prep and ACPI drivers in the past. Doesn't seem to be a straightforward way to fix this in every similar situation. The reference link seems to be dead unfortunately. Thanks again for the help!

You could also just boot into Win7PE then use the DriverInjection app (Google DriverInjection.exe) to inject the appropriate controller driver into the system hive. Worked well for me when needing to install and change the storage controller on a P2V ESXi Server 2003 VM. You'll need the txtsetup.oem file for the driver you're looking to install, however.

-Gray Fox

If you are using recovery mode, you'll likely want to open regedit and then open the correct hive from your source disk. HKLM\SYSTEM here's an article on how to do that:

-registry-offline-windows-re/

Paragon released a tool that was still free until 2010. It was called "paragon adaptive restore". If you can find the freeware version then this tool automatically sets the storage (and other drivers such as troublesome VGA) to "defaults".

Sorry for gravedig but this is still high on google results for p2v 7b errors

This is still valid today, although for some reason the Shift-F10 trick to get into the command prompt didn't work. I had to cancel the automatic repair, then use the "advanced options". But after that it was easy.

Thanks!

setting LSI_SAS to 0 worked for me with exporting a windows 7 x64 machine from virtual box to Qubes-OS. Version 4.0RC3 uses the mptsas1068 SCSI controller which is loaded by windows only when LSI_SAS is set this way.

This is awesome and would like to say big thank you to Andrew. you save me huge times ....

The LSI_SAS changed to 0 fixed my issue - I had a look on my vm and the SCSI controller set LSI Logic SAS which makes sense with the changes.

This article discusses complete file details, SYS file troubleshooting instructions for problems with intelide.sys, and a comprehensive set of free downloads for every file version that has been catalogued by our team.

There are a number of reasons why you could be encountering issues with intelide.sys. Most of the issues concerning sys files involve Blue Screen of Death (BSOD) errors. These types of intelide.sys errors can be cause by hardware problems, outdated firmware, corrupt drivers, or other software-related (eg. Microsoft Office Access 2010 update) issues. Some of these errors include:

GEEK TIP : As a rule of thumb, it's always a good idea to create a Windows "Snapshot" backup / System Restore Point before making any hardware or software changes to your computer. That way, it's very easy to restore your system in the unfortunate event you encounter a intelide.sys Blue Screen of Death error after recent changes.

If you're encountering one of the error messages above, follow these troubleshooting steps to resolve your intelide.sys issue. These troubleshooting steps are listed in the recommended order of execution.

When the first two steps haven't solved your issue, it might be a good idea to run Windows Update. Many intelide.sys error messages that are encountered can be contributed to an outdated Windows Operating System. To run Windows Update, please follow these easy steps:

If none of the previous three troubleshooting steps have resolved your issue, you can try a more aggressive approach (Note: Not recommended for amateur PC users) by downloading and replacing your appropriate intelide.sys file version. We maintain a comprehensive database of 100% malware-free intelide.sys files for every applicable version of Microsoft Office Access 2010. Please follow the steps below to download and properly replace you file:

GEEK TIP : We must emphasize that reinstalling Windows will be a very time-consuming and advanced task to resolve intelide.sys problems. To avoid data loss, you must be sure that you have backed-up all of your important documents, pictures, software installers, and other personal data before beginning the process. If you are not currently backing up your data, you need to do so immediately.

CAUTION : We strongly advise against downloading and copying intelide.sys to your appropriate Windows system directory. Microsoft typically does not release Microsoft Office Access 2010 SYS files for download because they are bundled together inside of a software installer. The installer's task is to ensure that all correct verifications have been made before installing and placing intelide.sys and all other SYS files for Microsoft Office Access 2010. An incorrectly installed SYS file may create system instability and could cause your program or operating system to stop functioning altogether. Proceed with caution.

There isn't sufficient quota available to create the virtual machine: You can check the available quota by going to Subscription -> Usage + quotas. You can open a new support request to increase the quota.

You're trying to failover virtual machines of different size families in same availability set. Ensure that you choose same size family for all virtual machines in the same availability set. Change size by going to Compute settings of the virtual machine and then retry failover.

Site Recovery wasn't able to create a network interface for the failed over virtual machine. Make sure you have sufficient quota available to create network interfaces in the subscription. You can check the available quota by going to Subscription -> Usage + quotas. You can open a new support request to increase the quota. If you have sufficient quota, then this might be an intermittent issue, try the operation again. If the issue persists even after retries, then leave a comment at the end of this document.

To bring up any machine in Azure, the Azure environment requires some of the drivers to be in boot start state and services like DHCP to be in autostart state. Thus, hydration activity, at the time of failover, converts the startup type of atapi, intelide, storflt, vmbus, and storvsc drivers to boot start. It also converts the startup type of a few services like DHCP to autostart. This activity can fail due to environment specific issues.

In case the VM meets no-hydration requirement, the script gives the result "This system meets no-hydration requirement". In this case, all drivers and services are in the state as required by Azure and hydration on the VM isn't required.

Test failover or failover operation can fail for a machine with the error "One or more replica IP addresses for the network adapter of virtual machine is invalid", if proper cleanup of a previous test failover operation didn't happen. Due to this, the test machine might still be present in Azure environment and it might be using the same IP address. It causes the target configuration of virtual machine to become critical.

3a8082e126