locked
Windows 7 Blue Screen - netbios.sys error RRS feed

  • Question

  • When Installing Windows 7 I get aboout 70% done and the system has to reboot itself.  When it does it says starting services and then goes to the blue screen.  It says the netbios.sys file is read only and can't be changed.  Setup faiules each time and goes into a continuous reboot loop.  I have a Acer Machine (2.16 ghz) pletny of ram, etc.

    In looking at the setuperr.log file I see this:

    2009-05-07 18:40:27, Error                        Number of Enumerated Devices = 13[gle=0x00000103]
    2009-05-07 18:40:28, Error                        Failed to find driver file path. Error=00000002x
    2009-05-07 18:40:28, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:40:28, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:40:28, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:40:28, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:40:29, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:40:29, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-05-07 18:40:29, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-05-07 18:40:29, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:40:29, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-05-07 18:40:29, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-05-07 18:40:33, Error                        Number of Enumerated Devices = 13[gle=0x00000103]
    2009-05-07 18:40:35, Error                        Failed to find driver file path. Error=00000002x
    2009-05-07 18:40:35, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:40:35, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:40:35, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:40:35, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:40:36, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:40:36, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-05-07 18:40:36, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-05-07 18:40:36, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:40:36, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-05-07 18:40:36, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-05-07 18:41:34, Error                        Number of Enumerated Devices = 13[gle=0x00000103]
    2009-05-07 18:41:34, Error                        Failed to find driver file path. Error=00000002x
    2009-05-07 18:41:34, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:41:34, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:41:34, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:41:34, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:41:35, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:41:35, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-05-07 18:41:35, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-05-07 18:41:35, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:41:35, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-05-07 18:41:35, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-05-07 18:41:39, Error                        Number of Enumerated Devices = 13[gle=0x00000103]
    2009-05-07 18:41:40, Error                        Failed to find driver file path. Error=00000002x
    2009-05-07 18:41:40, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:41:40, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:41:40, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:41:40, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:41:41, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:41:41, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-05-07 18:41:42, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-05-07 18:41:42, Error                        Failed to find driver file path. Error=00000002x[gle=0x80092004]
    2009-05-07 18:41:42, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-05-07 18:41:42, Error                        Failed to find driver file path. Error=ffffffffx[gle=0x00000003]
    2009-05-07 18:55:50, Error      [0x0808fe] MIG    Plugin {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}: BthMig: Failed to migrate bthport keys, bailing out


    Has anybody seen this or know how to get around this issue?

    Friday, May 8, 2009 2:27 PM

Answers

  • I had the same problem upgrading from Windows Vista Ultimate to Windows 7 RTM, "... failed to migrate ... bailing out".  I have no bluetooth. Looking at the Windows Compatibility report it recommended uninstalling programs including Network Monitor 3 and Windows Mobile Device Centre 6.1.  I uninstalled these as well Vodafone Mobile Connect Lite V 9.3.3.10523, Winpcap and Wireshark.  I have a Vodafone/Huawei K3715 USB Data Modem and an HP iPAQ PDA.

    The final result was a successful upgrade.

    I suggest the title be changed to "Windows 7 Upgrade problem - {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}: BthMig: Failed to migrate bthport keys."

    I also had instability after rollback.  I bypassed this by starting in safe mode, shutting down, then starting as normal.

     
    Sunday, August 16, 2009 3:56 PM

All replies

  • I dug thru setupact.log and found these entries that point to the issue:

    2009-05-07 18:55:50, Warning    [0x0809c7] MIG    COutOfProcPluginFactory::CreateInstance: [D:\$WINDOWS.~BT\Sources\ReplacementManifests\Microsoft-Windows-BTH-USER\bthmigplugin.dll, {E0CBF06C-CD8B-4647-BB8A-263B43F0F974}] does not support interface {CCEC0752-DC07-4C83-A9F1-3CC9D1A1822F}.
    2009-05-07 18:55:50, Warning    [0x080386] MIG    Failure while instantiating IPreGather for Plugin={ServerPath="Microsoft-Windows-BTH-USER\bthmigplugin.dll", CLSID={e0cbf06c-cd8b-4647-bb8a-263b43f0f974}, ThreadingModel=Apartment}. Error: 0x80004002
    2009-05-07 18:55:50, Info       [0x080722] MIG    Calling IDiscovery::Gather for Plugin={ServerPath="Microsoft-Windows-BTH-USER\bthmigplugin.dll", CLSID={e0cbf06c-cd8b-4647-bb8a-263b43f0f974}, ThreadingModel=Apartment}, userContext: System
    2009-05-07 18:55:50, Info                  MIG    IDiscovery::Gather for Plugin={ServerPath="Microsoft-Windows-BTH-USER\bthmigplugin.dll", CLSID={e0cbf06c-cd8b-4647-bb8a-263b43f0f974}, ThreadingModel=Apartment} - Working directory: C:\$UPGRADE.~OS\OnlineUpgradeGatherWork\agentmgr\CCSIAgent\005AF8C8
    2009-05-07 18:55:50, Info       [0x0808fe] MIG    Plugin {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}: BthMig: Collecting Bluetooth settings
    2009-05-07 18:55:50, Info       [0x0808fe] MIG    Plugin {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}: BthMig: BthMigLibDeleteRegKey to delete existing Bluetooth devices failed with hresult code 0x80070002
    2009-05-07 18:55:50, Warning    [0x0808fe] MIG    Plugin {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}: BthMig: Fail to open the BTHPORT key with Hresult 0x80070002
    2009-05-07 18:55:50, Error      [0x0808fe] MIG    Plugin {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}: BthMig: Failed to migrate bthport keys, bailing out



    I don't understand why it us 'Collecting Bluetooth settings'.  I don't use anything bluetooth on this pc.

    Friday, May 8, 2009 3:39 PM
  • I have the same problem upgrading a machine which was previously upgraded from XP SP2 to Vista Home Premium

    2009-05-05 20:44:31, Error      [0x0808fe] MIG    Plugin {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}: BthMig: Failed to migrate bthport keys, bailing out

    I don't have any bluetooth devices either!

    I used the Win7 RC
    Friday, May 8, 2009 7:49 PM
  • I had the same problem upgrading from Windows Vista Ultimate to Windows 7 RTM, "... failed to migrate ... bailing out".  I have no bluetooth. Looking at the Windows Compatibility report it recommended uninstalling programs including Network Monitor 3 and Windows Mobile Device Centre 6.1.  I uninstalled these as well Vodafone Mobile Connect Lite V 9.3.3.10523, Winpcap and Wireshark.  I have a Vodafone/Huawei K3715 USB Data Modem and an HP iPAQ PDA.

    The final result was a successful upgrade.

    I suggest the title be changed to "Windows 7 Upgrade problem - {e0cbf06c-cd8b-4647-bb8a-263b43f0f974}: BthMig: Failed to migrate bthport keys."

    I also had instability after rollback.  I bypassed this by starting in safe mode, shutting down, then starting as normal.

     
    Sunday, August 16, 2009 3:56 PM
  • Looks like it cant find the path something like unbinding but i dont really know why that is trying to migrate to bluetooth port!
    wait for the spcialist for some proper help!!!
    Best regards,
    RR
    Sunday, August 16, 2009 6:21 PM
  • I ran into the same situation (also on a system, which was previously upgraded from Windows XP to Vista).
    Trying to delete the registry key with the mentioned value {e0cbf06c-cd8b-4647-bb8a-263b43f0f974} fails. Also if I run regedit as Administrator and try to take ownership of the key and objects in it, the subkey Properties denies access.
    Finally, after a reboot and uninstalling a Sony Ericsson phone application I was able to take the ownership and delete the key. But seems setup locked up again with no response to keyboard and mouse and no disk activity.
    Deleting all the bth keys and the files didn't bring any success as well, Win7 setup froze again with that value in setuperr.log.
    This is getting funny ...
    Best greetings from Germany
    Olaf
    Saturday, September 5, 2009 7:47 PM
  • I am having the same issue. I managed to delete all the KEYs but still getting the same error and setup hangs at the same point. Win7 upgrade is really lousy. Lousy job by MS.
    Thursday, September 17, 2009 5:09 PM
  • Seems I'm not alone in having this bluetooth migration error and I don't have anything bluetooth.  I had no issues at all installing the Win7 beta or RC (granted on a separate partition, but I tried doing Win7 as a clean install so there wouldn't be anything to migrate technically, though to be fair the logs I looked at were from the last attempt which was an upgrade path after reinstalling Vista without issue).

    I have seen several posts on similar issues, it seems this is a point that needs to be escalated higher as a very real bug in the install routine.

    The closest I have to something bluetooth is my cordless mouse.  It isn't listed as bluetooth, but again the RC had no issues with my equipment.

    Sigh.
    Monday, October 26, 2009 1:15 AM
  • I am in the same situation sadly.  I've never installed any sort of blutooth device on this PC yet I'm having errors related to one.  Thank you Microsoft.
    Thursday, February 11, 2010 9:41 PM