This article was previously published under Q157924
Retired KB Content Disclaimer
This article was written about products for which Microsoft no longer offers support. Therefore, this article is offered "as is" and will no longer be updated.
When you restart Windows 95 after installing a program or making aconfiguration change to your computer, you may receive one of thefollowing error messages:
Windows initializing device IOS: Windows protection error. IOS failed to Initialize, Please restart
While initializing IOS: Windows protection error. You need to restart your computer.
Windows initializing device IOS: Windows protection error. You need to restart your computer.
After the error message is displayed, you may not be able to start Windows95 normally. However, you should be able to start Windows 95 in Safe mode.
It may also be possible to start Windows 95 normally after using thefollowing procedure:
Boot Windows 95 in Safe mode or to a command prompt.
Perform one of the following two steps:
Edit the Config.sys and Autoexec.bat files and disable any references to Smartdrv.exe. To disable a line, type rem at the beginning of the line.
Rename Smartdrv.exe to another name.
Restart your computer normally.
For additional information about IOS error messages, click the article numbers below to view the articles in the Microsoft Knowledge Base:
225497 Windows 95 May Fail to Boot Due to I/O Subsystem Failure
164666 You receive the "While initializing device IOS a Windows protection error occurred" error message when you start Windows 95
192841 Difficulties Using AMD K6-2 or Athlon Central Processing Unit
168866 FIX: IOS Failed to Initialize Error During Installation
Microsoft has confirmed this to be a problem in Microsoft Windows 95 andOEM Service Releases. This issue is resolved by the following updated file for Windows 95and OSR2:
RMM.PDR version 4.00.1112 (dated 03/10/97) and later
The problem occurs only on certain system configurations, and does notoccur if Internet Explorer 4.0 is installed on your computer. These systemconfigurations have a minimum of 32 MB of RAM and a large number of devicedrivers. The problem is rare and can occur only at startup. Users whosesystems are starting successfully today are not impacted.