Windows - No Disk error

Discussion in 'Other ESET Home Products Beta' started by tjg79, Jan 11, 2010.

Thread Status:
Not open for further replies.
  1. tjg79

    tjg79 Registered Member

    Joined:
    Jan 11, 2010
    Posts:
    55
    Location:
    Virginia, USA
    I recently upgraded from ESET SS v3 to v4.2 Beta. My system locks up on the regular v4. My OS is Win XP Pro x64.

    I've been getting a pop-up error box indicating "Windows - No Disk..." everytime I disconnect a USB device such as a memory stick or floppy. The error box is difficult to dismiss.

    Anyone have similar problems? I suspect it's an OS side effect from the ESET SS program.

    When I google the error, I see that there are numerous causes. Some are related to malware. Since I've only experienced this issue since I've upgraded my ESET, I suspect the two are related.

    Does anyone have any ideas?

    Regards to all.
     
  2. Cvigunenko

    Cvigunenko Registered Member

    Joined:
    Jan 11, 2010
    Posts:
    6
    If at you suspicion, on the harmful software, or viruses.
    1) Download Dr.Web CureIt!
    2) Spend fast check
    3) Spend full check
    4) Remove all that it will find.
    5) Download Malwarebytes' Anti-Malware
    6) Establish
    7) Update
    :cool: Spend full check
    9) All found remove.
     
  3. Cudni

    Cudni Global Moderator

    Joined:
    May 24, 2009
    Posts:
    6,963
    Location:
    Somethingshire
    does it only happen with usb devices? What is the exact error message?
     
  4. tjg79

    tjg79 Registered Member

    Joined:
    Jan 11, 2010
    Posts:
    55
    Location:
    Virginia, USA
    Cudni,

    Yes, I'm only experiencing the problem when I remove a USB device from the system. The system acts as if the USB device wasn't stopped properly. I've removed USB devices in the past, without properly stopping them, and never had any issues.


    The error pop-up box says:

    The box has three buttons: Cancel, Try Again & Continue.

    Cvigunenko,

    Thank you for the malware removal procedure. I'll give it a try.
     
    Last edited: Jan 11, 2010
  5. Cvigunenko

    Cvigunenko Registered Member

    Joined:
    Jan 11, 2010
    Posts:
    6
    And if you completely remove the ESS. And reboot your PC, the problem remains?
     
  6. tjg79

    tjg79 Registered Member

    Joined:
    Jan 11, 2010
    Posts:
    55
    Location:
    Virginia, USA
    I haven't tried that yet. I'm hoping to be able to tweak the system to resolve the issue. I've ordered a couple of windows xp books to see if there is a less drastic approach to the solution.
     
  7. Cvigunenko

    Cvigunenko Registered Member

    Joined:
    Jan 11, 2010
    Posts:
    6
    If you remove the ESS and the problem remains, so that's not the ESS. Also try to roll back Windows to a date when the problem was not observed.
     
  8. toasale

    toasale Registered Member

    Joined:
    Apr 19, 2006
    Posts:
    86
    Location:
    Alabama
    USB flash drives should never be ejected without properly stopping their service. Pulling a stick out improperly can cause data loss/corruption, as you do not know when a device is communicating with a file(s) it has linked to. Drivers and other files in the OS are required upon insertion and ejection of a device and this is why proper ejection is necessary.

    I'm sure most, if not all, of us have ejected a device improperly and many of us have payed a price for this. :eek: :D
     
  9. tjg79

    tjg79 Registered Member

    Joined:
    Jan 11, 2010
    Posts:
    55
    Location:
    Virginia, USA
    I've only occasionally failed to properly stop a USB device before removing it. I've never done it intentionally. However, my "Windows - No Disk" error is not a result of failing to properly stop the device. The error occurs after every removal of a USB memory stick with proper stopping.
     
  10. techie007

    techie007 Registered Member

    Joined:
    Jan 2, 2008
    Posts:
    125
    Location:
    Ontario, Canada
    From http://www.consumingexperience.com/2007/11/windows-no-disk-exception-processing.html:

    They provide step-by-step instructions for each of these options at that site -- hopefully one of them will help. :) Since USB is being mentioned in this thread, I'd say check into Option 2 first.
     
  11. tjg79

    tjg79 Registered Member

    Joined:
    Jan 11, 2010
    Posts:
    55
    Location:
    Virginia, USA
    Thanks Techie007.

    I saw that after doing some google searches. I didn't think it would resolve my issue for the following reasons:

    1. I've scanned my system with serval malware, antivirus and malicious softeware programs, in addition to my ESET Smart Security v4.2 Beta and did not get any detections.

    2. Drive letter changes: I don't think that will be a enduring solution. The drive letters for the USB devices appear when the device is installed and disappear when they are removed. Any changes will probably only remain for as long as the device is detected. When you re-attach the device, you start the issue all over again.

    3. I don't usually have a floppy drive on my system. The motherboard does not have a floppy controller. I have a USB floppy that I used to install the operating system (F6 proceedure) drivers when I installed the operating system. I've only used the USB floppy drive a few times and like I've said, it's not normally attatched to the system.

    4. Uninstalling and reinstalling certain programs seems like a temporary fix. If this works, what's the likelihood that the error won't happen again in the future? I plan to reinstall the operating system any way, because I want the system to have a C:\ drive address. Presently, it has an I:\ drive address. I couldn't get the operating system to assign C:\ to my RAID disk. I've done some research on the Microsoft site and I think I may be able to get the RAID disk a "C" drive letter if I remove all other USB devices and disconnect the USB floppy, before the operating system assigns the drive letter.

    5. I don't want to just address the symtom, by disabling the error message in the registry. I want to try to fix the registry to fix the actual problem. I'd like to be able to understand the registry better so I know what I'm doing. That's why I'm waiting for some reference books to arrive.

    I suspect the issue is related to my ESET SS v4.2 software, becasue that's the last change to my system that seems to be about the time these errors started to occur.

    By the way, I sent a support request to ESET tech support more than 24 hours ago and I haven't seen a response yet.

    Thanks to all for your suggestions.

    Regards
     
  12. Cvigunenko

    Cvigunenko Registered Member

    Joined:
    Jan 11, 2010
    Posts:
    6
    If you want to reinstall Windows is the most optimal solution to install it from CD.
     
  13. tjg79

    tjg79 Registered Member

    Joined:
    Jan 11, 2010
    Posts:
    55
    Location:
    Virginia, USA
    Update:

    I haven't resolved my issue, but I know that after I removed my HP Photosmart C7250 All-in-One software, the issue appears to be completely resolved.

    Now I'm going to see if there is a way to reinstall the HP software that doesn't cause the issue to return.
     
  14. whftherb

    whftherb Registered Member

    Joined:
    Mar 6, 2007
    Posts:
    16
    Remember that most of these AIO printers these days have memory card/stick readers designed and embedded in their hardware. Those devices are given a USB spigot to do I/O in. Your error could be related to the memory card slot being misconfig'd and not unplugging a standard USB device from, say, the front panel. I agree with uninstalling the HP package. Let it run a day or so without it - see if the error appears still. In fact, what I would have done is simply unplug the whole printer and see if the error occurs. That way you've narrowed it down.

    GL.


    H
     
  15. tjg79

    tjg79 Registered Member

    Joined:
    Jan 11, 2010
    Posts:
    55
    Location:
    Virginia, USA
    Yes, my HP Photosmart C7250 All-in-One has card/stick readers. When the Photosmart is connected to the pc, I get a drive "J:" icon under Devices with Removable Storage in My Computer as well as the scanner icon under Scanners and Cameras. I may have unintentionally stopped the USB drive "J:" when removing a memory stick from another drive. I can't recall exactly, but perhaps that's when I started to get the Windows - No Disk error. After I removed the HP software, I didn't get any more errors.

    I have since reinstalled the software and I get an occasional No Disk error when I'm using the Photosmart. But, the error is infinitely easier to dismiss. So, I think the error is entirely related to the HP Photosmart and not my ESET Smart Security v4.2 Beta which was why I posted on this forum in the first place.

    I contacted HP tech support for assistance in reinstalling the HP software. We were unsuccessful at installing the latest version 10 for Win XP Pro x64 distributed from the HP website. The tech indicated I had a bad USB cable and ordered me a new one under warranty. I found another USB cable about two hours after that tech support incident and attempted another install with HP tech support. The second attempt was unsuccessful as well so we installed the earlier version 9 successfully from a CD which indicates to me that the USB cable is probably ok.

    The fact that I can't successfully install the latest HP software from their website indicates to me that there is still an unresolved issue with this Photosmart. The original HP tech rep indicated that he would contact me again when the new USB cable arrives. I'll try to install the latest HP software again with HP tech support after I get the new cable. If the install with version 10 is still unsuccessful, perhaps HP will send me a new Photosmart.
     
    Last edited: Jan 27, 2010
Thread Status:
Not open for further replies.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.