• Welcome to Tux Reports: Where Penguins Fly. We hope you find the topics varied, interesting, and worthy of your time. Please become a member and join in the discussions.

"wscript.exe - No Disk" error

J

Jose

Flightless Bird
On Feb 2, 12:06 am, samah <sa...@mymail.com> wrote:
> Jose wrote:
> > On Jan 31, 11:50 pm, samah <sa...@mymail.com> wrote:
> >> Jose wrote:
> >>> On Jan 28, 1:32 am, samah <sa...@mymail.com> wrote:
> >>>> Win XP SP3.
> >>>> After I eject a CD/DVD from my DVD drive or unmount an disk image from
> >>>> the Daemon Tools virtual drive, I get an error window with the title
> >>>> "wscript.exe - No Disk" and with the message " There is no disk in the
> >>>> drive. Please insert a disk into drive (drive letter):". There are three
> >>>> buttons that I can click: Cancel, Try again, Continue. When I click any
> >>>>    of these options, the error window closes but pops up again after an
> >>>> interval of approx. i minute. The only way I can close this window
> >>>> permanently is by rebooting the system.
> >>>> Can anybody help me with this please.
> >>>> Thanks in advance.
> >>>> -samah.
> >>> Start here:
> >>> Be sure the referenced file really does not exist in system32.
> >>> Using regedit, navigate to:
> >>> HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
> >>> On the right side look for Shell which should have value of just:
> >>> explorer.exe
> >>> Delete anything after explorer.exe if there is anything.
> >>> Perform some scans for malicious software, then fix any remaining
> >>> issues:
> >>> Download, install, update and do a full scan with these free malware
> >>> detection programs:
> >>> Malwarebytes (MBAM):  http://malwarebytes.org/
> >>> SUPERAntiSpyware: (SAS):  http://www.superantispyware.com/
> >>> They can be uninstalled later if desired.
> >>> Under that same key look for Userinit which should have value of just:
> >>> C:/WINDOWS\system32\userinit.exe,
> >>> Do not delete the comma, but delete everything after it (your issue
> >>> most likely)
> >> Since I have found the referenced file in the system32 folder, I have
> >> not proceeded with your suggestion. Now how to go about it?

>
> >> Thank you for your valuable time.

>
> > My post is a generic one that will apply to most people most of the
> > time.

>
> > That script is a generic one found in many places on the Internet as
> > the "fix all your problems" script.

>
> > You should stick with MBAM and SAS for general scanning.

>
> > If the script file does not exist on your system, it was removed by a
> > scanning program or by hand.  All of the things you have been trying
> > are confusing and so far are not working.  The location of the problem
> > is not something that will reveal itself in msconfig or any of the
> > other methods suggested for things to try.

>
> > You need things to do and you need to stop trying things that don't
> > work if you want to fix this!

>
> > Check in Task Manager and if wscript.exe is running, terminate it and
> > remove the mentioned.vbs file, then fix the registry Userinit section
> > as indicated.

>
> > The entry in the registry (most likely Userinit) is still broken, so
> > you need to fix that either by hand, or you can fix it using
> > HijackThis and it will find and fix it for you.  If you run
> > HijackThis, it will report a single F2 item and there should not be an
> > F2 item on most systems and you can let HijackThis fix it for you.  It
> > will look like this (which is wrong).

>
> > F2 - REG:system.ini: UserInit=C:/WINDOWS\SYSTEM32\Userinit.exe, c:
> > \windows\system32\wscript.exe c:/windows\system32\killvirus.vbs

>
> > Get the 2.0.2 version of HijackThis (not the Beta) here:

>
> >http://free.antivirus.com/hijackthis/

>
> > If you are worrried about your registry, back it up first with this
> > popular free tool:

>
> >http://www.larshederer.homepage.t-online.de/erunt/

>
> > The other possibility is that the reference is in the autorun.inf file
> > for your device - you can check the content of your autorun.inf file
> > for the device that is complaining and post the contents here if you
> > can't figure it out.

>
> Followed your advice and fixed the problem successfully.
>
> Here is what I did:
> 1. Deletedkillvirus.vbs in system32.
> 2. In the Registry, Userinit had the value of:
> C:/WINDOWS\system32\userinit.exe,  C:/WINDOWS\system32\wscript.exe
> C:/WINDOWS\system32\killvirus.vbs.
>     Deleted everything after userinit.exe, as you advised.
>
> In the process you introduced some very useful utilities to me. Thank
> you so much for everything.


Of course, and thank goodness.

Everything makes perfect sense when things are understood!

I would recommend this ASAP:

Download, install, update and do a full scan with these free malware
detection programs:

Malwarebytes (MBAM): http://malwarebytes.org/
SUPERAntiSpyware: (SAS): http://www.superantispyware.com/

They can be uninstalled later if desired.
 
S

samah

Flightless Bird
Jose wrote:
> On Feb 2, 12:06 am, samah <sa...@mymail.com> wrote:
>> Jose wrote:
>>> On Jan 31, 11:50 pm, samah <sa...@mymail.com> wrote:
>>>> Jose wrote:
>>>>> On Jan 28, 1:32 am, samah <sa...@mymail.com> wrote:
>>>>>> Win XP SP3.
>>>>>> After I eject a CD/DVD from my DVD drive or unmount an disk image from
>>>>>> the Daemon Tools virtual drive, I get an error window with the title
>>>>>> "wscript.exe - No Disk" and with the message " There is no disk in the
>>>>>> drive. Please insert a disk into drive (drive letter):". There are three
>>>>>> buttons that I can click: Cancel, Try again, Continue. When I click any
>>>>>> of these options, the error window closes but pops up again after an
>>>>>> interval of approx. i minute. The only way I can close this window
>>>>>> permanently is by rebooting the system.
>>>>>> Can anybody help me with this please.
>>>>>> Thanks in advance.
>>>>>> -samah.
>>>>> Start here:
>>>>> Be sure the referenced file really does not exist in system32.
>>>>> Using regedit, navigate to:
>>>>> HKLM\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
>>>>> On the right side look for Shell which should have value of just:
>>>>> explorer.exe
>>>>> Delete anything after explorer.exe if there is anything.
>>>>> Perform some scans for malicious software, then fix any remaining
>>>>> issues:
>>>>> Download, install, update and do a full scan with these free malware
>>>>> detection programs:
>>>>> Malwarebytes (MBAM): http://malwarebytes.org/
>>>>> SUPERAntiSpyware: (SAS): http://www.superantispyware.com/
>>>>> They can be uninstalled later if desired.
>>>>> Under that same key look for Userinit which should have value of just:
>>>>> C:/WINDOWS\system32\userinit.exe,
>>>>> Do not delete the comma, but delete everything after it (your issue
>>>>> most likely)
>>>> Since I have found the referenced file in the system32 folder, I have
>>>> not proceeded with your suggestion. Now how to go about it?
>>>> Thank you for your valuable time.
>>> My post is a generic one that will apply to most people most of the
>>> time.
>>> That script is a generic one found in many places on the Internet as
>>> the "fix all your problems" script.
>>> You should stick with MBAM and SAS for general scanning.
>>> If the script file does not exist on your system, it was removed by a
>>> scanning program or by hand. All of the things you have been trying
>>> are confusing and so far are not working. The location of the problem
>>> is not something that will reveal itself in msconfig or any of the
>>> other methods suggested for things to try.
>>> You need things to do and you need to stop trying things that don't
>>> work if you want to fix this!
>>> Check in Task Manager and if wscript.exe is running, terminate it and
>>> remove the mentioned.vbs file, then fix the registry Userinit section
>>> as indicated.
>>> The entry in the registry (most likely Userinit) is still broken, so
>>> you need to fix that either by hand, or you can fix it using
>>> HijackThis and it will find and fix it for you. If you run
>>> HijackThis, it will report a single F2 item and there should not be an
>>> F2 item on most systems and you can let HijackThis fix it for you. It
>>> will look like this (which is wrong).
>>> F2 - REG:system.ini: UserInit=C:/WINDOWS\SYSTEM32\Userinit.exe, c:
>>> \windows\system32\wscript.exe c:/windows\system32\killvirus.vbs
>>> Get the 2.0.2 version of HijackThis (not the Beta) here:
>>> http://free.antivirus.com/hijackthis/
>>> If you are worrried about your registry, back it up first with this
>>> popular free tool:
>>> http://www.larshederer.homepage.t-online.de/erunt/
>>> The other possibility is that the reference is in the autorun.inf file
>>> for your device - you can check the content of your autorun.inf file
>>> for the device that is complaining and post the contents here if you
>>> can't figure it out.

>> Followed your advice and fixed the problem successfully.
>>
>> Here is what I did:
>> 1. Deletedkillvirus.vbs in system32.
>> 2. In the Registry, Userinit had the value of:
>> C:/WINDOWS\system32\userinit.exe, C:/WINDOWS\system32\wscript.exe
>> C:/WINDOWS\system32\killvirus.vbs.
>> Deleted everything after userinit.exe, as you advised.
>>
>> In the process you introduced some very useful utilities to me. Thank
>> you so much for everything.

>
> Of course, and thank goodness.
>
> Everything makes perfect sense when things are understood!
>
> I would recommend this ASAP:
>
> Download, install, update and do a full scan with these free malware
> detection programs:
>
> Malwarebytes (MBAM): http://malwarebytes.org/
> SUPERAntiSpyware: (SAS): http://www.superantispyware.com/
>
> They can be uninstalled later if desired.


Thank you.
 
Top