Windows Vista users using Intel Storage Driver (iastor.sys) may fail to upgrade to Windows 7. Microsoft acknowledged this issue through KB 2008373. Using the step-by-step guide, users can successfully upgrade Vista to Windows 7.
When a user using Intel Storage Driver tries to upgrade to the next Windows operating system, they may get the following error message:
\$windows.~bt\windows\system32\drivers\iastor.sys
Status: 0xc0000359
Windows failed to load because a critical system driver is missing or corrupt
Microsoft identified the cause of this error. In response to the error at the KB 2008373 page, the Redmond software giant said, “during (the) upgrade process the incorrect version of the iastor is referenced resulting in the above error.” The cause is identified, the solution is available too.
The KB (Knowledge Base) post directs users through the process of resolving the error. The necessary steps as posted on the KB post to resolve the error is discussed below. After you complete the steps, you can upgrade your Vista machine to Windows 7.
- Access Driver Repository Folder under C:\Windows\System32\DriverStore\FileRepository and move any folders that contain the file:
iastor.infto a temporary location.
To move the files from the FileRepository you may need additional permissions which can be accomplished by taking ownership of the folder:
- Right-click on the folder and choose Properties.
- Click Security tab > Advanced button.
- Click Owner tab > Edit button > Select your account.
- Search for references to iastor within the oem inf files in the c:\windows\inf folder.
For Example: findstr \i \c:”iastor” %windir%\inf\oem*.inf
- Make a note of the oem##.inf files reported where ## is a numeral. Move the oem##.inf and corresponding oem##.pnf from c:\windows\inf folder to a temporary folder.
- Delete $~bt, $~LS and $~Upgrade folders from c:\ drive if they exist
- Download and install the latest version of the iastor.sys driver from Intel website on the Vista machine: http://downloadcenter.intel.com/.
- Start the Windows 7 upgrade process. It should complete successfully now.
Once the Upgrade process has completed successfully, there is no need to restore the iastore files, or the oem*.inf and oem*.pnf files back to their original location as the devices will no longer be needed.
Im trying to install windows 7 on a second partition in ssd (windows 8.1 is installed in the first partition) but i keep getting this message from this forum thread: http://www.windows-n…ration-manager/ but i have no idea how to do the solution written there. I have unallocated space ready in my second partition to install windows 7 in it. The disk is GPT. I have been trying to make UEFI Bootable (GPT) usb sticks using rufus that i can then use to install my windows7 BUT every time i get stuck in this problem and i don’t understand how the solution works. task sequence with 64 bit boot image? etc.
my motherboard is asus z97 gamer pro. There are bunch of uefi/cms/secure boot options currently uefi is enabled. I am pretty new to this stuff and my goal is to dualboot windows 7 and 8 64bit both inside 1 ssd into different partitions.
Edit: Was able to install win8 as a dualboot to ssd’s third partition after removing hdd, didn’t try with the above method though. Also running diskpart > list disk > select disk x > /clean and doing Bootrec /FIXBOOT , Bootrec /FIXMBR from recovery menu cmd (shift+f10) might have helped.
Introduction
More and more UEFI based hardware is being used in organizations and these UEFI based systems are being imaged via UEFI network boot via Configuration Manager 2012 R2.
Problem
Up until the introduction of UEFI hardware, most organizations use 32 bit (x86) boot images to deploy both 32bit and 64 bit operating systems.
UEFI hardware however requires a that the boot image must match the architecture of the device it’s booting on otherwise it will fail to boot.
So for example, you must use a 64 bit boot wim if the UEFI hardware itself is 64 bit, similarly you must use a 32 bit boot wim if the UEFI hardware is 32 bit. In most cases I’ve dealt with however, the UEFI hardware (for example Surface Pro 3) is already 64bit therefore it would require a 64 bit boot wim.
If you UEFI network boot 64 bit UEFI hardware in an environment that responds with a 32bit boot image, you’ll see the following error
“File: \Windows\System32\boot\winload.efi Status: 0xc0000359”
as shown in the screenshot below
Solution
There are a few solutions to this problem, but basically all involve the same thing, make sure that the task sequence deployment that ‘answers’ your UEFI hardware, uses a boot image (wim) that matches the architecture of your UEFI hardware, and in most cases that is a 64 bit boot image as shown below:
The LIFO rule
The task sequence deployment that answers the network boot request will be from the last task sequence deployed to the collection that your computer you are booting is a member of.
I call this the LIFO rule, as in Last In First Out.
You can either add the computer in question (computer+mac address) to a collection that has a task sequence deployed to it with a 64bit boot image or re-deploy a task sequence with a 64 bit boot image to the collection that this computer is a member of, or change the current task sequence to use a 64 bit boot wim instead of a x86 bit boot wim.
If you cannot make a change to any of the UEFI Network deployments then another idea is to use Standalone or boot media containing the 64bit boot image.
Be aware that changing the architecture of your boot wim may cause some executables to fail to run in Windows PE as the ‘subsystem’ in WinPE will have changed architecture from 32bit to 64bit. This also means that you can only install a 64 bit operating system using this boot image.
“To install Windows to an EFI-based computer, you must enable EFI mode in the computer’s firmware and boot with 64-bit pre-installation media. ” – source, Technet.
Once you’ve made the changes above, UEFI network boot a client computer again, and you should see it’s using the boot.wim file (package ID) that you attached to the task sequence, in this case it’s using a 64bit boot wim (P0100002.wim)
as you can see here…
The end result, is a working UEFI network boot !
cheers
niall
Windows 10: \windows\system32\boot\winload.efi status: 0xc0000359 solution
Discus and support \windows\system32\boot\winload.efi status: 0xc0000359 solution in Windows 10 BSOD Crashes and Debugging to solve the problem; I just recently got my hand on a refurbished computer that can with Windows 10 home. Everything was going fine, I was doing my usual stuff along with…
Discussion in ‘Windows 10 BSOD Crashes and Debugging’ started by DilucRagnvindr, Dec 11, 2020.
-
\windows\system32\boot\winload.efi status: 0xc0000359 solution
I just recently got my hand on a refurbished computer that can with Windows 10 home. Everything was going fine, I was doing my usual stuff along with my art commissions when I get a notification from the computer telling me that I needed to restart my computer. I restarted it and booted it back up, only to be met with a blue screen that read:
«Your PC/Device needs to be repaired
The application or operating system couldn’t be loaded because a required file is missing or contains errors.
File: \windows\system32\boot\winload.exe
Error Code: 0xc000000f
You’ll need to use recovery tools. If you don’t have any installation media like a disc or USB drive, contact your PC administrator or PC/Device manufacturer
Press enter to try again does nothing
Press F8 for Startup settings does nothing»Of course, I ended up downloading the tool to fix it and plugged it in but when I do it says that everything in my computer is fine and nothing can be fixed and that it *should* start normally..I feel the need to mention that I load the 64x version since the 32x version fails to load in the first place.
Should I just cave and buy the repair disk? I’ve followed many tutorials so far on how to fix this and so far I’ve gotten nothing..
-
Which tool to recover the EFI partition? Booted into Rescue Disk That’s not what they suggest here:
FIX: Steps to Fix Winload.EFI Error — Appuals.com
Winload.EFI Error, is pretty much self explanatory by it’s name is an error that prevents windows from loading. This is usually caused by corrupt boot records or incorrect boot configuration. Depending on your Operating System, the error message may vary but the keyword winload.efi will be same. On a Windows 8/8.1/10 system, the error usually pops-up in the following form.
-
Windows boot winload efi error 0000e9
hi my acer swift ryzen laptop completly crashed the weekend with the winload efi error .
ive gone into bios and disabled secure boot in uefi but no result . Ive managed to download windows 10 on usb drive and set it up in bios to boot from that drive however i still get the same blue window as before even tho the usb is top of the boot list.
I want to go into advanced options but it doesnt appear on the blue screen and now mot sure what to do . Any help would be great , i dont want to wipe the machine if possible -
\windows\system32\boot\winload.efi status: 0xc0000359 solution
Windows 10: Getting blue screen error messsage «windows\system32\winload..efi» and error code «0xc000000f».
Original Title: windows 10 0xc000000f error in lenovo pc
my laptop is lenovo g50 30 which is windows 8.1 build.
after upgrade it shows blue screen
windows\system32\winload..efi
error code 0xc000000f
i cant find the solution in community
\windows\system32\boot\winload.efi status: 0xc0000359 solution
-
\windows\system32\boot\winload.efi status: 0xc0000359 solution — Similar Threads — windowssystem32bootwinload efi status
-
error code 0xc0000359
in Windows 10 Gaming
error code 0xc0000359: I have read all I can find on this and come to the conclusion I need to do a fresh install. Problem occurred after switching to outlook from windows mail, subsequent updates have cause windows 10 not to boot. I have created media creation tool and it gets to error code… -
error code 0xc0000359
in Windows 10 Software and Apps
error code 0xc0000359: I have read all I can find on this and come to the conclusion I need to do a fresh install. Problem occurred after switching to outlook from windows mail, subsequent updates have cause windows 10 not to boot. I have created media creation tool and it gets to error code… -
error code 0xc0000359
in Windows 10 Installation and Upgrade
error code 0xc0000359: I have read all I can find on this and come to the conclusion I need to do a fresh install. Problem occurred after switching to outlook from windows mail, subsequent updates have cause windows 10 not to boot. I have created media creation tool and it gets to error code… -
EFI
in Windows 10 Gaming
EFI: https://docs.microsoft.com/zh-cn/windows-server/storage/disk-management/extend-a-basic-volumehttps://answers.microsoft.com/en-us/windows/forum/all/%E6%97%A0%E6%B3%95%E6%89%A9%E5%B1%95efi%E7%B3%BB/1659d1ee-5722-4456-8d0e-ed65c781fdbe
-
Windows does not start, gives an error 0xc0000359
in Windows 10 BSOD Crashes and Debugging
Windows does not start, gives an error 0xc0000359: Yesterday my laptop only had the logo when I wanted to start. I tried to install win 10 but it doesn’t work. Just have this error 0xc0000359 on the screen. Is there an option to fix it?… -
0xc0000359
in Windows 10 Installation and Upgrade
0xc0000359: Yeasterday my ntb had just logo when i wanted start it. I tried install win 10 but doesnt work. Just have this mistake on screen. Win 10 from usb normally works on other pc but on my not. Is any option how can i fix it? [IMG]… -
Installing Windows 10 x86 on a .vhd, 0xC0000359 when trying to boot
in Windows 10 Virtualization
Installing Windows 10 x86 on a .vhd, 0xC0000359 when trying to boot: My host OS is Windows 10 Pro 1703 x64 (updating to 1710 as soon as released) on UEFI.
I created a blank .vhd file and initialized it (yes, I did use GPT), and I used the Windows AIK to install Windows 10 Pro 1703 x86 on it, and it shows in the boot menu, but when I try to… -
Windows Boot Manager EFI\Microsoft\boot\bcd status 0xc0000225
in Windows 10 Support
Windows Boot Manager EFI\Microsoft\boot\bcd status 0xc0000225: Hello allI am currently having trouble booting into windows 10.I have tried to do a automatic repair from the media creation tool, troubleshoot using command prompt. I have tried using diskpart but nothing works, i dont know if i missing something please help….
-
Fail to boot: winload.efi missing; error 0xc0000359
in Windows 10 Installation and Upgrade
Fail to boot: winload.efi missing; error 0xc0000359: I upgraded ok with the update and successfully activated windows 10. I downloaded both 32bit and 64bit to usb using media creation tool as I wanted to clean install Windows 10 64bit on my 64bit compatible machine although am currently running 32bit windows 7 as that’s what I…
Users found this page by searching for:
-
Windows\system32\boot\winload.efi error 0x0000359
,
-
uefi is supported windows\system32\boot\winload.exe
,
-
cara mengatasi error 0xc0000359
,
- mengatasi eror 0xc0000359,
- 0xc0000359,
- error code 0xc0000359,
- Error code 0xc0000359 on windows 10