himem.sys file is missing?

I cannot open windows because the himem.sys file is missing,what shall i do?
Who is Participating?
ViRoyConnect With a Mentor Commented:
copy himem.sys off any computer (with exact same version of windows) and put it into your c:\

then use a boot disk and goto a c:\ prompt (dont need cd-rom support)

make sure this is the FIRST line in there


then restart and youll be all good.
The himem.sys file lives in the c:\windows folder. Boot to the command prompt. Type edit c:\config.sys and press enter. When the Config.sys file comes up make sure that the top line is as follows: Device=C:\windows\Himem.sys

If the line is not there type it in. Make sure it is the first line. If it is there at the top, exit the editor. If your mouse isn't working press the alt key, enter key and the n the up error key. Press enter again.

CD to the windows folder (type cd windows and press enter). When at the c:\windows prompt type dir himem.* and press enter. If the file isn't found you must copy it from a startup floppy or other source.

Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

If you have Windows startup disk, Himem.sys placed on that.

You are new here so I will say this nicely: We don't post an answer until asked. We also don't take someone elses comment and post it as an answer. That is called POINT STEALING!!!!!!!

Just comments, really.

This is my 2nd attempt at a session, so plz forgive where needed.  I'm still learning on locked or not, and will work out on points later. That said,

I cannot yet tell difference between a question of theory (say by a student studying for a test) or by someone with a real problem, for which I'd like more elaboration (say a student who cannot personally access the network any more, including both school and this site). b23 brevity to this date could fit either case (to me) - any pointers appreciated.

From the armchair: For a real problem, cumbo response seems best 1st attempt at resolution, but may be incomplete not knowing what it was that actually broke the system.

The points aside, I have seen too many cases where placing major O/S files anywhere other than default (like \Windows) can lead to problems down the road, even if successful for the 'current' problem, especially moving them to the root.  Just a word of caution on abusing the root directory.

Most interesting was nestiam response, for since I never noauto'd, I had no clue on such a potential.  It now seems possible to me that some 'Install' I ran, that went awry, might have done that to me.

So I'll add to y'all a reminder to make yourself a good, proven boot diskette, with reliable config.sys, for example. AND a copy of


For I think it was that backup-type method that helped me get the needed fix (while knowing more about noauto could have made it unecessary). It is also could defense to ensure the DOS editor is really available at that time. Too often, it is not, needing another workaround to implement any of these responses.

All Courses

From novice to tech pro — start learning today.