VFAT Error

Recently, I have encountered the VFAT error. I conducted
a search of the Microsoft KB for VFAT, and discovered
Microsoft KB article ID - 139063 that addresses this
issue. This article provides six options to resolve this
problem. However, I wasn't sure about the intent of
option three, which addresses the use of the Ifshlp.sys
statement as follows:

If the following Ifshlp.sys statement is deleted from the
Config.sys file
after you reinstall Windows: DEVICE=C:\Windows\Ifshlp.sys

First, I didn't have to reinstall Windows; it is the
existing operating system. Second, should the Config.sys
file have a Ifshlp statement (i.e.,
Device=C:\Windows\Ishlp.sys) as indicated? I accessed the
Config.sys in safe mode and safe mode prompt only and it
does not appear to have this statement. Should I edit the
Config.sys and add this line?

If anyone could respond to my questions in options 3, it
would be greatly appreciated.

Regards,

Paul Spinn
(home)
(work)

quoting:
Recently, I have encountered the VFAT error. I conducted
a search of the Microsoft KB for VFAT, and discovered
Microsoft KB article ID - 139063 that addresses this
issue. This article provides six options to resolve this
problem. However, I wasn't sure about the intent of
option three, which addresses the use of the Ifshlp.sys
statement as follows:

If the following Ifshlp.sys statement is deleted from the
Config.sys file
after you reinstall Windows: DEVICE=C:\Windows\Ifshlp.sys

First, I didn't have to reinstall Windows; it is the
existing operating system. Second, should the Config.sys
file have a Ifshlp statement (i.e.,
Device=C:\Windows\Ishlp.sys) as indicated? I accessed the
Config.sys in safe mode and safe mode prompt only and it
does not appear to have this statement. Should I edit the
Config.sys and add this line?

If anyone could respond to my questions in options 3, it
would be greatly appreciated.

Regards,

Paul Spinn


option 3, yes that is a very common cause of the VFAT errors. Adding the
line to your config.sys will fix it. Why does it happen? Normally windows
should load ishlp.sys automatically, but for some oddball reason or perhaps
something changed settings... then it will cause windows not to load
ishlp.sys automatically, so adding it to config.sys will fix it up.