TechSpot

Windows 7 MTP driver not working

By orondf
Oct 10, 2011
Post New Reply
  1. Hi,

    I have Windows 7 Home Premium 64bit
    Whenever I connect my Nokia C7 to a USB port, the driver for MTP doesn't work.
    I get a Code 31 error: "This device is not working properly because Windows cannot load the drivers required for this device."

    Nokia Ovi Suite still works, but I can't load the phones' music library, and I have to use the Nokia Phone Browser to browse folders on my phone.
    I used to have no problem with MTP with a Sony Ericsson W980, but at some point it stopped working and only Mass Storage mode worked.

    Any ideas how to fix this without reinstalling Windows? Thanks in advance.

    PS: I recently started getting a Code 19 error for the Nokia drivers that were ok: "Windows cannot start this hardware device because its configuration information (in the registry) is incomplete or damaged."
    This Code 19 error seems to have no effect.

    Update: Forgot to mention that I have to wait 2 minutes after connecting my phone, for the software to start.
     
  2. LookinAround

    LookinAround TechSpot Chancellor Posts: 8,374   +167

    Don't know if this might apply to your case but i've seen reports in other forums about iTunes interfering with the MTP driver, Nokia phones (and Nikon cameras too). Do you have (or had) iTunes installed?

    Here's why: "Filters" are device driver add-on parts. (Filters are supposed to work with drivers. But if a filter goes bad the whole driver can go bad) iTunes installs filters that may corrupt a driver for use by some non-iTunes devices

    Let's check to see what filters are installed for both your MTP and CD/DVD device.
    > Open Device Manager, select any one of your DVD drives
    > Right click Properties->Details
    > Scroll through the pull down menu to see both Class Upper Filters and Class Lower Filters
    > If you see any filters listed you should be able to copy/paste or report what you see listed in your next post

    Repeat and also report any Class Upper/Lower filters listed for your MTP device. (p.s. ignore Device Filters, we only want to look at Class Upper/Lower filters if any on your CD/DVD drive and MTP device)

    Click thumbnail for example of Class Upper and Lower Filters on my own computer for my DVD drive
    [​IMG]
     
  3. orondf

    orondf TS Member Topic Starter Posts: 95

    I haven't installed itunes. I will check the filters in a few hours.
     
  4. orondf

    orondf TS Member Topic Starter Posts: 95

    DVD drive (LG GH24NS50):
    Class Lower Filters:
    ElbyCDFL
    PxHlpa64


    MTP Device
    No filters.
     
  5. LookinAround

    LookinAround TechSpot Chancellor Posts: 8,374   +167

    Interesting... Don't know if this will lead anywhere BUT
    > Both those filters are installed by 3rd party products (they're not from Microsoft)
    > Do you have CloneCD installed? (i googled and think they install the Elby... filter)
    > Not yet sure about other

    What CD/DVD related products do you have installed? (I wonder if one of them is interfering just as iTunes sometimes does)

    Let me know and i'll get back to you later and what to try next
     
  6. orondf

    orondf TS Member Topic Starter Posts: 95

    I think I had this problem ever since I installed Samsung Kies (because I needed to connect to my sister's phone). I tried uninstalling it when the problem started, but it didn't help. Even System Restore didn't fix this.



    I have the following CD/DVD burning products:
    CloneCD
    ImgBurn
    BurnOn CD&DVD
    MagicISO

    I will probably uninstall CloneCD.
     
  7. LookinAround

    LookinAround TechSpot Chancellor Posts: 8,374   +167

    When you do, check if the Elby filter was also removed

    fyi.. Another source of filter problems i've found and traced back to filters: A 3rd party uninstaller deletes its filter file from disk but not its reference in the registry. So when Windows uses the driver, it sees the filter reference in the registry but no file for it to load, so it can't start the driver and KA-BOOM!
     
  8. orondf

    orondf TS Member Topic Starter Posts: 95

    I uninstalled CloneCD and the filter was removed.
     
  9. LookinAround

    LookinAround TechSpot Chancellor Posts: 8,374   +167

    It looks like the PxHlpa64.sys filter can be installed by several different 3rd party products. So let's check your driver files next. Open Device Manager, right click any DVD drive, select Properties->Driver tab then Driver Details button

    1. Do you see any driver file listed with filename starting Px? If not, you may have a registry reference to a non-existent driver file

    2. Select each driver file and see what company is listed as "Provider". Are all the files from Microsoft? (except the Px.. file i think will be from Sonic and my own 32bit DVD drivers also includes a UBHelper.sys displayed as "Unknown". But let me know if you see any files from other then M$)

    3. You can also check your MTP device for any driver files from other then M$

    /* edit */
    p.s. you probably already rebooted, just fyi: one needs to reboot after removing a filter to test the result

    /* edit 2 */
    another fyi for anyone reading..
    > A common misconception (i never knew myself till i discovered it one time) when you uninstall/reinstall a device in DevMgr, Windows only uninstalls/reinstalls the HARDWARE driver files. IT DOESN'T REMOVE 3RD PARTY CLASS FILTERS! that are used by companies to intercept and process device I/O to support their product.
    > Class upper/lower filters often added by iTunes, Acronis, Roxio, Nero, and many, many other companies.
    > Class filters are only removed by uninstalling the app or using a tool or editing registry by hand (but be careful!)
    > Instructions for removing CD/DVD and disk filters can be found in CD/DVD or Disk Problems? How to Fix Problems Caused by Filters
     
  10. orondf

    orondf TS Member Topic Starter Posts: 95

    For DVD, I found PxHlpa64.sys from Sonic.
    For MTP, all drivers are Microsoft.
     
  11. LookinAround

    LookinAround TechSpot Chancellor Posts: 8,374   +167

    OK. I'm less suspicious of PxHlpa filter now since
    > We know the driver file exists on your disk
    > This filter from Sonic is used by several different companies and products (vs. the Elby filter from CloneDVD which, like the filter that gets installed by iTunes, is a filter for a specific product)
    > We'll come back to it later if need be

    But since you said you installed Samsung Kies.. go to CtlPnl->Programs and Features and check that you uninstalled two different things: one is for Samsung Kies and other for Samsung USB drivers
     
     
  12. orondf

    orondf TS Member Topic Starter Posts: 95

    Sorry, been very busy in past 2 weeks.
    I found Samsung USB Drivers and uninstalled it. After restarting, the problem still wasn't fixed.
     
  13. LookinAround

    LookinAround TechSpot Chancellor Posts: 8,374   +167

    No problem. Cool to just post back whenever you have the time/can :)

    As to your problem, next thing we'll look at and try....
    p.s. I'm trying to explain a bit of what i'm doing and why, in case it might help anyone who comes across this thread in future. Of course, I'm also hoping this leads to a successful conclusion for you too!

    fyi: By default, Windows Device Manager only displays devices it currently detects. Drivers for a Plug and Play device are installed when the PnP device is first plugged in and detected. But those device drivers aren't removed when the PnP device is simply disconnected but rather when the PnP device is uninstalled! So old drivers for old devices are often still on a system even though the device no longer appears in Device Manager if a device was simply disconnected but it was never uninstalled)

    This tool should show me all the devices and drivers still installed on your machine. (I'm not sure exactly what I'm looking for but will see if anything jumps out at me - especially if any old phone or MTP or WPD devices/drivers are listed!) WPD = Windows Portable Device

    See How To Report Your Computer's Device Manager Data
     
  14. orondf

    orondf TS Member Topic Starter Posts: 95

    I have attached the file.
     

    Attached Files:

  15. orondf

    orondf TS Member Topic Starter Posts: 95

    Maybe there is a way to reinstall the WPD drivers?

    Update: Nokia has removed the phone browser in the new version, so now I have to set my phone to mass storage before connecting it, otherwise I can't browse the files.
     
  16. LookinAround

    LookinAround TechSpot Chancellor Posts: 8,374   +167

    Sometimes i think understanding Windows devices and drivers is a "black art". fyi... What i've figured out to date on that subject is, at best, a lighter shade of grey. ;) So, I don't want to sound the expert but rather have managed to have some idea of how some devices and drivers get installed and work

    MTP devices and their drivers are relatively new. From what i've seen they also install a bit different then other Windows devices (and with a new set of rules) So i'll only comment now on some devicesi saw in your DevMgr report that you still have installed. I haven't yet had the time to look closer at MTP (but happy to as it's also an opportunity for me to learn)

    p.s. i think our next eventual step will be to uninstall all the MTP devices but, if ok, don't want to that yet till i look further (will try to not make that too much longer)

    Devices i see installed
    1) Various instances of Nokia devices are installed - no surprise but there are multiple instances we'll remove
    2) But I also see a Sony Ericsson USB portable device?
    3) There;s also USB disks installed for
    > Nokia C7-00
    > OLYMPUS FE310,X840,C
    > Sony Camcorder USB D
    > Sony Ericsoon Memory Stick
    4) More portable devices
    > A couple from SanDisk
    > and a Sony Ericsson phone?

    Do all these devices sound familiar? Which devices are old and which do you still need / use?
     
  17. LookinAround

    LookinAround TechSpot Chancellor Posts: 8,374   +167

    I think trying to cleanup the old USB storage, WPD and MTP drivers on your machine just got easier.

    While looking further at your problem, I just discovered that a tool i like to use (for USB storage driver cleanup) has been updated to include removing old Windows Portable Devices (which should include MTP drivers) as well

    1. Create a System Restore point
    2. I haven't had time to update my old guide but see How to Cleanup and Remove old USB Storage Drivers. Include the following steps to the ones in the Guide (as appropriate)
    > Download version 0.80 of the drivecleanup tool HERE
    > Unzip. Since you're running 64bit Windows, copy the 64bit version of the tool (in the X64 folder) to C:\Windows\System32
    > Disconnect all your old USB WPD devices (cams, phones, etc). Disconnect USB disks as well
    > Open a Elevated commmand prompt and enter
    Code:
    drivecleanup.exe -R
    > You can capture the output by right clicking on the command window title bar then Edit->Select All then Edit->Copy. Paste the result to save it to your next post
    > Now replug your Nokia. Should do a clean reinstall. Any luck?

    /* edit */
    Here's sample output using the newer version of the tool
    Code:
    DriveCleanup V0.8.0 (Win32)
    Uninstalls non present USB hubs, USB storage devices and their storage volumes, Disks, CDROMs, Floppies, WPD devices
    and deletes their registry items
    Freeware by Uwe Sieber - www.uwe-sieber.de
    
    removing USB device 'USB\VID_04E8&PID_685E&MI_03\7&B64610&1&0003'
     OK
    removing USB device 'USB\VID_04E8&PID_685E&MI_00\7&B64610&1&0000'
     OK
    removing USB device 'USB\VID_04E8&PID_685E&MI_01\7&B64610&1&0001'
     OK
    removing USB device 'USB\VID_04E8&PID_685E&MI_03\7&B64610&1&0003'
     OK
    removing USB device 'USB\VID_0424&PID_3803\5&109970AE&0&8'
     OK
    removing USB device 'USB\VID_04E8&PID_685E&MI_01\7&B64610&1&0001'
     OK
    removing Disk device 'USBSTOR\DISK&VEN_ANDROID&PROD___UMS_COMPOSITE&REV___00\8&D70C5AC&0&46411931BC54228E&0'
     OK
    removing Disk device 'USBSTOR\DISK&VEN_ANDROID&PROD___UMS_COMPOSITE&REV___00\8&D70C5AC&0&46411931BC54228E&1'
     OK
    removing volume 'STORAGE\VOLUME\_??_USBSTOR#DISK&VEN_ANDROID&PROD___UMS_COMPOSITE&REV___00#8&D70C5AC&0&46411931BC54228E&0#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B}'
     OK
    removing volume 'STORAGE\VOLUME\_??_USBSTOR#DISK&VEN_ANDROID&PROD___UMS_COMPOSITE&REV___00#8&D70C5AC&0&46411931BC54228E&1#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B}'
     OK
    removing WPD device 'WPDBUSENUMROOT\UMB\2&37C186B&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_ANDROID&PROD___UMS_COMPOSITE&REV___00#8&D70C5AC&0&46411931BC54228E&1#'
     OK
    removing WPD device 'WPDBUSENUMROOT\UMB\2&37C186B&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_ANDROID&PROD___UMS_COMPOSITE&REV___00#8&D70C5AC&0&46411931BC54228E&0#'
     OK
    
    Removed 3 USB devices
    Removed 3 USB hubs
    Removed 2 Disk devices
    Removed 0 CDROM devices
    Removed 0 Floppy devices
    Removed 2 Storage volumes
    Removed 2 WPD devices
    Removed 0 Keys from registry
    USB device to remove: 'USB\VID_04E8&PID_685E&MI_03\7&B64610&1&0003'
    USB device to remove: 'USB\VID_04E8&PID_685E&MI_00\7&B64610&1&0000'
    USB device to remove: 'USB\VID_04E8&PID_685E&MI_01\7&B64610&1&0001'
    USB device to remove: 'USB\VID_04E8&PID_685E&MI_03\7&B64610&1&0003'
    USB device to remove: 'USB\VID_0424&PID_3803\5&109970AE&0&8'
    USB device to remove: 'USB\VID_04E8&PID_685E&MI_01\7&B64610&1&0001'
    Disk device to remove: 'USBSTOR\DISK&VEN_ANDROID&PROD___UMS_COMPOSITE&REV___00\8&D70C5AC&0&46411931BC54228E&0'
    Disk device to remove: 'USBSTOR\DISK&VEN_ANDROID&PROD___UMS_COMPOSITE&REV___00\8&D70C5AC&0&46411931BC54228E&1'
    Volume to remove: 'STORAGE\VOLUME\_??_USBSTOR#DISK&VEN_ANDROID&PROD___UMS_COMPOSITE&REV___00#8&D70C5AC&0&46411931BC54228E&0#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B}'
    Volume to remove: 'STORAGE\VOLUME\_??_USBSTOR#DISK&VEN_ANDROID&PROD___UMS_COMPOSITE&REV___00#8&D70C5AC&0&46411931BC54228E&1#{53F56307-B6BF-11D0-94F2-00A0C91EFB8B}'
    WPD device to remove: 'WPDBUSENUMROOT\UMB\2&37C186B&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_ANDROID&PROD___UMS_COMPOSITE&REV___00#8&D70C5AC&0&46411931BC54228E&1#'
    WPD device to remove: 'WPDBUSENUMROOT\UMB\2&37C186B&0&STORAGE#VOLUME#_??_USBSTOR#DISK&VEN_ANDROID&PROD___UMS_COMPOSITE&REV___00#8&D70C5AC&0&46411931BC54228E&0#'
    
    3 USB devices not removed
    3 USB hubs not removed
    2 Disk devices not removed
    2 Storage volumes not removed
    2 WPD devices not removed
    Press any key to close
     
  18. orondf

    orondf TS Member Topic Starter Posts: 95

    Hi,
    Still not working. Here is the drivecleanup:

    Code:
    DriveCleanup V0.8.0 (x64)
    Uninstalls non present USB hubs, USB storage devices and their storage volumes, Disks, CDROMs, Floppies, WPD devices
    and deletes their registry items
    Freeware by Uwe Sieber - www.uwe-sieber.de
    
    Regkey delete HKLM\System\MountedDevices\\??\Volume{ea6b3bc9-333e-11e0-b88a-806e6f6e6963}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{ea6b3bd2-333e-11e0-b88a-806e6f6e6963}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{91317d40-3791-11e0-88cf-1c6f65886e17}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{91317d42-3791-11e0-88cf-1c6f65886e17}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{f2097f0c-3f57-11e0-a1f7-1c6f65886e17}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{f2097f8a-3f57-11e0-a1f7-1c6f65886e17}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{edeca88f-429c-11e0-b4b1-1c6f65886e17}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{3230310c-43dc-11e0-8954-1c6f65886e17}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{c90d16cd-5087-11e0-9e96-1c6f65886e17}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{87b37be0-52c0-11e0-ae56-1c6f65886e17}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{87b37be2-52c0-11e0-ae56-1c6f65886e17}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{c6fbe217-5ee6-11e0-945a-1c6f65886e17}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{c6fbe219-5ee6-11e0-945a-1c6f65886e17}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{34775e4a-75d0-11e0-a049-1c6f65886e17}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{87487b11-8ed4-11e0-bfe3-806e6f6e6963}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{87487b14-8ed4-11e0-bfe3-806e6f6e6963}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{87487b17-8ed4-11e0-bfe3-806e6f6e6963}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{87487b1a-8ed4-11e0-bfe3-806e6f6e6963}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{a1f93aa6-90f4-11e0-ab65-1c6f65886e17}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{15d03c73-91f8-11e0-a9d8-1c6f65886e17}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{09bfbe85-9e39-11e0-b676-1c6f65886e17}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{09bfbe89-9e39-11e0-b676-1c6f65886e17}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{c726ef4b-bf63-11e0-8a04-806e6f6e6963}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{ace8fca0-c8e9-11e0-ba48-005056c00008}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{ace8fca2-c8e9-11e0-ba48-005056c00008}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{b86f5f54-d70c-11e0-bd16-005056c00008}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{c1d91030-f8d7-11e0-9a75-08002700341f}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{ca87dcf4-0148-11e1-b883-08002700341f}
     OK
    Regkey delete HKLM\System\MountedDevices\\??\Volume{ca87dcfa-0148-11e1-b883-08002700341f}
     OK
    Regkey delete HKLM\System\MountedDevices\#{ca87dcf9-0148-11e1-b883-08002700341f}
     OK
    Regkey delete HKLM\System\MountedDevices\#{8e4a241f-07c5-11e1-9be9-08002700341f}
     OK
    Regkey delete HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\H
     OK
    Regkey delete HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\I
     OK
    Regkey delete HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\J
     OK
    Regkey delete HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\MountPoints2\L
     OK
    
    Removed 35 Keys from registry
    
    
    This output doesn't look right...

    another thing:

    I don't need the Sony Ericsson phone drivers. (SanDisk was installed twice because I have 2, right?)

    I don't know what this means:
     
  19. orondf

    orondf TS Member Topic Starter Posts: 95

    This problem is not a problem with my phone's driver; this is also a problem with ANY MTP device such as my brother's sansa MP3 player.
     
  20. LookinAround

    LookinAround TechSpot Chancellor Posts: 8,374   +167

    Sorry for the long delay to reply. But i've been busy as well i've been trying to look further into MTP and WPD devices and drivers in Windows. I must admit there's still LOTS I don't understand about MTP / WPD so I don't know I'll be able to help you solve this short of you having to reinstall :(

    But before that last resort here's a couple more things

    1) re: drivecleanup. Yes, your drivecleanup output doesn't look right BECAUSE i gave you the wrong command line option :eek: (sorry!) The -r option i gave you only removes registry entries (which explains your output). Run it again without any options, simply
    Code:
    drivecleanup
    2) fyi. I tried drivecleanup again on my own machine: I found that while it removes LOTS of unneeded stuff, it won't remove some types of MTP/WPD entries (nor do i know why it distinguishes some types vs others)

    We could try uninstalling the stuff left behind using the DevManView tool but i couldn't guarantee the result (i.e. maybe only something to try just short of being willing to do a reinstall, if need be)

    What we can try next
    > Disconnect your USB drives, cameras, WPD devices etc. and re-run drivecleanup as simply drivecleanup
    > Try reconnecting an MTP device
    > Then lets see if the Windows Event Log might have any more detail about the error if it still occurs
    > Post a copy of recent Windows Event Log entries. See here
    ===> To run it under W7, you'll need to right click it then select Run as Administrator
    ===> Be patient. It may take a minute or two for its output window to appear
     
  21. orondf

    orondf TS Member Topic Starter Posts: 95

    Well, it still doesn't work. Here is the events:
    Vino's Event Viewer v01c run on Windows 2008 in English
    Report run at 30/12/2011 9:21:59 AM

    Note: All dates below are in the format dd/mm/yyyy

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    'Application' Log - Critical Type
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Log: 'Application' Date/Time: 23/06/2011 10:18:06 AM
    Type: Critical Category: 0
    Event: 2 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
    The application (Virtual PC 2007, from vendor Microsoft) was hard-blocked and raised the following: Virtual PC 2007 is not supported on this version of Windows. For more information, contact Microsoft.

    Log: 'Application' Date/Time: 23/06/2011 10:17:40 AM
    Type: Critical Category: 0
    Event: 2 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
    The application (Virtual PC 2007, from vendor Microsoft) was hard-blocked and raised the following: Virtual PC 2007 is not supported on this version of Windows. For more information, contact Microsoft.

    Log: 'Application' Date/Time: 23/06/2011 10:16:42 AM
    Type: Critical Category: 0
    Event: 2 Source: Microsoft-Windows-ApplicationExperienceInfrastructure
    The application (Virtual PC 2007, from vendor Microsoft) was hard-blocked and raised the following: Virtual PC 2007 is not supported on this version of Windows. For more information, contact Microsoft.

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    'Application' Log - Error Type
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Log: 'Application' Date/Time: 30/12/2011 2:23:34 AM
    Type: Error Category: 0
    Event: 72 Source: SideBySide
    Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

    Log: 'Application' Date/Time: 28/12/2011 11:39:23 PM
    Type: Error Category: 0
    Event: 72 Source: SideBySide
    Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

    Log: 'Application' Date/Time: 28/12/2011 7:31:32 PM
    Type: Error Category: 0
    Event: 12293 Source: VSS
    Volume Shadow Copy Service error: Error calling a routine on a Shadow Copy Provider {b5946137-7b9f-4925-af80-51abd60b20d5}. Routine details Cannot ask provider {b5946137-7b9f-4925-af80-51abd60b20d5} if volume is snapshotted. [0x8000ffff] [hr = 0x8000ffff, Catastrophic failure ].

    Log: 'Application' Date/Time: 28/12/2011 7:31:11 PM
    Type: Error Category: 100
    Event: 1000 Source: Application Error
    Faulting application name: vlc.exe, version: 1.1.11.0, time stamp: 0x4e1edf37 Faulting module name: vlc.exe, version: 1.1.11.0, time stamp: 0x4e1edf37 Exception code: 0xc0000005 Fault offset: 0x00001883 Faulting process id: 0xa78 Faulting application start time: 0x01ccc597255afff7 Faulting application path: C:\Program Files (x86)\VideoLAN\VLC\vlc.exe Faulting module path: C:\Program Files (x86)\VideoLAN\VLC\vlc.exe Report Id: 7f577c31-318a-11e1-a467-08002700ecd3

    Log: 'Application' Date/Time: 28/12/2011 4:15:28 PM
    Type: Error Category: 100
    Event: 1000 Source: Application Error
    Faulting application name: vlc.exe, version: 1.1.11.0, time stamp: 0x4e1edf37 Faulting module name: vlc.exe, version: 1.1.11.0, time stamp: 0x4e1edf37 Exception code: 0xc0000005 Fault offset: 0x0000174c Faulting process id: 0x5d4 Faulting application start time: 0x01ccc57be8d2b9a0 Faulting application path: C:\Program Files (x86)\VideoLAN\VLC\vlc.exe Faulting module path: C:\Program Files (x86)\VideoLAN\VLC\vlc.exe Report Id: 27f334eb-316f-11e1-a467-08002700ecd3

    Log: 'Application' Date/Time: 28/12/2011 2:19:20 PM
    Type: Error Category: 100
    Event: 1000 Source: Application Error
    Faulting application name: jusched.exe, version: 2.0.6.1, time stamp: 0x4df127ab Faulting module name: USER32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba59 Exception code: 0xc0000005 Fault offset: 0x00029951 Faulting process id: 0x388 Faulting application start time: 0x01ccc56afd1d5092 Faulting application path: C:\Program Files (x86)\Common Files\Java\Java Update\jusched.exe Faulting module path: C:\Windows\syswow64\USER32.dll Report Id: ee4b64bc-315e-11e1-a467-08002700ecd3

    Log: 'Application' Date/Time: 28/12/2011 1:12:50 PM
    Type: Error Category: 100
    Event: 1000 Source: Application Error
    Faulting application name: jusched.exe, version: 2.0.6.1, time stamp: 0x4df127ab Faulting module name: USER32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba59 Exception code: 0xc0000005 Fault offset: 0x00029951 Faulting process id: 0xff8 Faulting application start time: 0x01ccc561b309fd43 Faulting application path: C:\Program Files (x86)\Common Files\Java\Java Update\jusched.exe Faulting module path: C:\Windows\syswow64\USER32.dll Report Id: a41568d4-3155-11e1-b747-08002700ecd3

    Log: 'Application' Date/Time: 28/12/2011 12:41:03 PM
    Type: Error Category: 100
    Event: 1000 Source: Application Error
    Faulting application name: jusched.exe, version: 2.0.6.1, time stamp: 0x4df127ab Faulting module name: USER32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba59 Exception code: 0xc0000005 Fault offset: 0x00029951 Faulting process id: 0xcb4 Faulting application start time: 0x01ccc55d3e94f67a Faulting application path: C:\Program Files (x86)\Common Files\Java\Java Update\jusched.exe Faulting module path: C:\Windows\syswow64\USER32.dll Report Id: 334aeec7-3151-11e1-98db-08002700ecd3

    Log: 'Application' Date/Time: 24/12/2011 6:49:29 PM
    Type: Error Category: 101
    Event: 1002 Source: Application Hang
    The program Explorer.EXE version 6.1.7601.17567 stopped interacting with Windows and was closed. To see if more information about the problem is available, check the problem history in the Action Center control panel. Process ID: a8c Start Time: 01ccc1744e8197d4 Termination Time: 0 Application Path: C:\Windows\Explorer.EXE Report Id: f9f83951-2e5f-11e1-ad49-08002700ecd3

    Log: 'Application' Date/Time: 23/12/2011 2:29:17 PM
    Type: Error Category: 0
    Event: 72 Source: SideBySide
    Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

    Log: 'Application' Date/Time: 23/12/2011 1:16:59 PM
    Type: Error Category: 100
    Event: 1000 Source: Application Error
    Faulting application name: jusched.exe, version: 2.0.6.1, time stamp: 0x4df127ab Faulting module name: USER32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba59 Exception code: 0xc0000005 Fault offset: 0x00029951 Faulting process id: 0xdf4 Faulting application start time: 0x01ccc174730989ca Faulting application path: C:\Program Files (x86)\Common Files\Java\Java Update\jusched.exe Faulting module path: C:\Windows\syswow64\USER32.dll Report Id: 64c3fc8e-2d68-11e1-ad49-08002700ecd3

    Log: 'Application' Date/Time: 21/12/2011 11:25:32 PM
    Type: Error Category: 0
    Event: 72 Source: SideBySide
    Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

    Log: 'Application' Date/Time: 21/12/2011 12:36:54 AM
    Type: Error Category: 0
    Event: 72 Source: SideBySide
    Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

    Log: 'Application' Date/Time: 19/12/2011 10:30:59 PM
    Type: Error Category: 0
    Event: 72 Source: SideBySide
    Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

    Log: 'Application' Date/Time: 19/12/2011 7:09:50 PM
    Type: Error Category: 100
    Event: 1000 Source: Application Error
    Faulting application name: jusched.exe, version: 2.0.6.1, time stamp: 0x4df127ab Faulting module name: USER32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba59 Exception code: 0xc0000005 Fault offset: 0x00029951 Faulting process id: 0xd68 Faulting application start time: 0x01ccbe81144ff91e Faulting application path: C:\Program Files (x86)\Common Files\Java\Java Update\jusched.exe Faulting module path: C:\Windows\syswow64\USER32.dll Report Id: 05929130-2a75-11e1-a8bb-08002700ecd3

    Log: 'Application' Date/Time: 19/12/2011 3:27:26 PM
    Type: Error Category: 0
    Event: 4003 Source: NovaBACKUP
    My Backup 2012 [Completed with errors], Monday, December 19, 2011 Objects Selected : 31
    Bytes Selected : 121.51 MB
    Objects Completed : 2
    Bytes Completed : 30.51 MB
    Start Time : 12/19/2011, 5:25:19 PM
    End Time : 12/19/2011, 5:27:26 PM
    Elapsed Time : 00:02:07
    3 Informational message(s), 1 warning(s), 1 error(s)
    Log file: C:\ProgramData\NovaStor\NovaStor NovaBACKUP\Logs\4eef575f.txt

    Log: 'Application' Date/Time: 18/12/2011 10:30:47 PM
    Type: Error Category: 0
    Event: 72 Source: SideBySide
    Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

    Log: 'Application' Date/Time: 17/12/2011 10:30:47 PM
    Type: Error Category: 0
    Event: 72 Source: SideBySide
    Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

    Log: 'Application' Date/Time: 16/12/2011 10:30:47 PM
    Type: Error Category: 0
    Event: 72 Source: SideBySide
    Activation context generation failed for "c:\program files\microsoft security client\MSESysprep.dll".Error in manifest or policy file "c:\program files\microsoft security client\MSESysprep.dll" on line 10. The element imaging appears as a child of element urn:schemas-microsoft-com:asm.v1^assembly which is not supported by this version of Windows.

    Log: 'Application' Date/Time: 16/12/2011 10:16:10 AM
    Type: Error Category: 100
    Event: 1000 Source: Application Error
    Faulting application name: jusched.exe, version: 2.0.6.1, time stamp: 0x4df127ab Faulting module name: USER32.dll, version: 6.1.7601.17514, time stamp: 0x4ce7ba59 Exception code: 0xc0000005 Fault offset: 0x00029951 Faulting process id: 0xe28 Faulting application start time: 0x01ccbbdb07a1a929 Faulting application path: C:\Program Files (x86)\Common Files\Java\Java Update\jusched.exe Faulting module path: C:\Windows\syswow64\USER32.dll Report Id: f9704267-27ce-11e1-a472-08002700ecd3

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    'System' Log - Critical Type
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Log: 'System' Date/Time: 08/12/2011 1:45:15 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 15/08/2011 4:45:38 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 09/08/2011 12:48:24 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 05/08/2011 1:32:10 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 02/08/2011 10:04:28 AM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 16/07/2011 11:35:32 AM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 03/07/2011 1:59:49 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    Log: 'System' Date/Time: 18/06/2011 7:22:26 PM
    Type: Critical Category: 63
    Event: 41 Source: Microsoft-Windows-Kernel-Power
    The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    'System' Log - Error Type
    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    Log: 'System' Date/Time: 28/12/2011 2:14:18 PM
    Type: Error Category: 0
    Event: 10016 Source: Microsoft-Windows-DistributedCOM
    The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

    Log: 'System' Date/Time: 28/12/2011 2:13:00 PM
    Type: Error Category: 0
    Event: 7023 Source: Service Control Manager
    The Diagnostic Policy Service service terminated with the following error: Access is denied.

    Log: 'System' Date/Time: 28/12/2011 2:12:46 PM
    Type: Error Category: 0
    Event: 46 Source: volmgr
    Crash dump initialization failed!

    Log: 'System' Date/Time: 28/12/2011 1:44:23 PM
    Type: Error Category: 0
    Event: 46 Source: volmgr
    Crash dump initialization failed!

    Log: 'System' Date/Time: 28/12/2011 1:43:47 PM
    Type: Error Category: 2
    Event: 55 Source: Ntfs
    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume Win7.

    Log: 'System' Date/Time: 28/12/2011 1:43:45 PM
    Type: Error Category: 2
    Event: 55 Source: Ntfs
    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume Win7.

    Log: 'System' Date/Time: 28/12/2011 1:43:44 PM
    Type: Error Category: 2
    Event: 55 Source: Ntfs
    The file system structure on the disk is corrupt and unusable. Please run the chkdsk utility on the volume Win7.

    Log: 'System' Date/Time: 28/12/2011 1:07:48 PM
    Type: Error Category: 0
    Event: 10016 Source: Microsoft-Windows-DistributedCOM
    The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

    Log: 'System' Date/Time: 28/12/2011 1:06:54 PM
    Type: Error Category: 0
    Event: 3002 Source: Microsoft Antimalware
    Microsoft Antimalware Real-Time Protection feature has encountered an error and failed. Feature: Behavior Monitoring Error Code: 0x80004005 Error description: Unspecified error Reason: The filter driver requires an up-to-date engine in order to function. You must install the latest definition updates in order to enable real-time protection.

    Log: 'System' Date/Time: 28/12/2011 1:06:37 PM
    Type: Error Category: 0
    Event: 7023 Source: Service Control Manager
    The Diagnostic Policy Service service terminated with the following error: Access is denied.

    Log: 'System' Date/Time: 28/12/2011 1:06:23 PM
    Type: Error Category: 0
    Event: 46 Source: volmgr
    Crash dump initialization failed!

    Log: 'System' Date/Time: 28/12/2011 1:06:16 PM
    Type: Error Category: 0
    Event: 46 Source: volmgr
    Crash dump initialization failed!

    Log: 'System' Date/Time: 28/12/2011 12:35:50 PM
    Type: Error Category: 0
    Event: 10016 Source: Microsoft-Windows-DistributedCOM
    The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID {C97FCC79-E628-407D-AE68-A06AD6D8B4D1} and APPID {344ED43D-D086-4961-86A6-1106F4ACAD9B} to the user NT AUTHORITY\SYSTEM SID (S-1-5-18) from address LocalHost (Using LRPC). This security permission can be modified using the Component Services administrative tool.

    Log: 'System' Date/Time: 28/12/2011 12:35:49 PM
    Type: Error Category: 0
    Event: 7022 Source: Service Control Manager
    The NovaStor NovaBACKUP Backup/Copy Engine service hung on starting.

    Log: 'System' Date/Time: 28/12/2011 12:34:21 PM
    Type: Error Category: 0
    Event: 7023 Source: Service Control Manager
    The Diagnostic Policy Service service terminated with the following error: Access is denied.

    Log: 'System' Date/Time: 28/12/2011 12:34:10 PM
    Type: Error Category: 0
    Event: 46 Source: volmgr
    Crash dump initialization failed!

    Log: 'System' Date/Time: 28/12/2011 12:34:05 PM
    Type: Error Category: 0
    Event: 46 Source: volmgr
    Crash dump initialization failed!

    Log: 'System' Date/Time: 24/12/2011 6:49:42 PM
    Type: Error Category: 0
    Event: 11 Source: Disk
    The driver detected a controller error on \Device\Harddisk3\DR8.

    Log: 'System' Date/Time: 24/12/2011 6:49:42 PM
    Type: Error Category: 0
    Event: 11 Source: Disk
    The driver detected a controller error on \Device\Harddisk3\DR8.

    Log: 'System' Date/Time: 24/12/2011 6:49:41 PM
    Type: Error Category: 0
    Event: 11 Source: Disk
    The driver detected a controller error on \Device\Harddisk3\DR8.

    the hard drive errors are probably because my external hdd isn't working very well.

    Thanks for all the help
     
  22. LookinAround

    LookinAround TechSpot Chancellor Posts: 8,374   +167

    The Event viewer logs don't seem to show anything helpful

    I also tried looking further into MTP/WPD drivers, their installs, dependencies, etc. but frankly the more I try to look and read, the more it makes my head spin! :dead: I'm sorry to say i don't think i can help fix your MTP driver problems :(

    Since it looks like your disk is also having errors, a clean reinstall on a new disk may be the best advice
    > An easy tool to look at your disk health status HERE
    > Also, before doing a fresh reinstall, make sure you know any activation IDs needed to reactivate any paid software you may need to reinstall that will need reactivating

    For future (to avoid reinstalls) you might periodically create disk image backups (so you can then restore a disk image of a working system). In general, I create a disk image backup every 3 months. I do data backups more frequently. Then it's a matter of you restoring the disk image followed by restoring your most recent data backup on top of the disk image restore
    I use Acronis True Image but EASUS ToDo Backup is a good freeware tool as well

    /* EDIT */
    We can still try to uninstall old MTP stuff still not yet removed if you;d like, but to repeat, it's best to only try that if you have everything backed up. I would GUESS that wouldn't make things any worse but can't guarantee as there's still much about MTP i don't understand. If you should want to try, run another DevManView for me so i can see what's still there and i can give you instruction
     
  23. orondf

    orondf TS Member Topic Starter Posts: 95

    Well, I don't have a backup, because I couldn't get it to backup all files and then update them each time, not overwrite or create a new backup. I should select "Differential" instead of "Incremental", right?
    Another question: Do I need to back up all my files or just drive C:?

    I don't think I am ready to do a clean install, I think I should reinstall or clone drive c: when I get another HDD (500GB just isn't enough). I can't get a new one untill the prices go down; Samsung 1TB currently costs 2.5x the original price!

    I still think we should try again and if I still have this problem when I get a new HDD, I will do a clean install.
    I think that we should remove the Microsoft VirtualPC drivers, because I use VirtualBox now instead.
     

    Attached Files:

    • dev.zip
      File size:
      19.3 KB
      Views:
      1
  24. LookinAround

    LookinAround TechSpot Chancellor Posts: 8,374   +167

    1) Please re-run DevManView. (see See How To Report Your Computer's Device Manager Data)
    I need its output saved as either "tabular text" or "comma delimited text". I can import those formats into Excel which makes it easy for me to manipulate and sort as columnar data (such as by Device Type).

    2. Hmm... Looks like EASUS released a new version of their backup tool since the last time i used it. I just did a quick look at their new version
    > Incremental vs. Differential will both create subsequent backups. (The difference is how they do it) Go ahead and use Incremental (Incrementals will use less space)
    > So do a full backup of your data. Then try incremental backups of your data
    > I notice EASUS will create a .PDB backup file for each backup. If you double click a backup file you can "explore" the backup and it should reflect the files at the time of the backup.

    If you also have the space to save a single backup of your C: drive, it helps assure you have everything as of "today" and can restore the full partition if needed. But whether you want to do it as well is up to you. I do things like that just to be extra cautious if the hard drive should unexpectedly fail.. then you have something you can also restore if need be

    /* EDIT */
    Oh. on that note, also click their Tools->Create rescue CD (or some similar name, i forget). This creates a rescue CD you can boot from the rescue CD if the hard drive should ever unexpectedly fail so you can restore to a new, empty disk if ever needed
     
  25. orondf

    orondf TS Member Topic Starter Posts: 95

    I attached the new DevManView file.

    About backing up: My external HDD isn't working well. If Windows starts up with the drive connected, it doesn't work, and reconnecting doesn't help. If I disconnect it and reboot, it works well, unless I reconnect it. I think this is because it is a 3.5" HDD with a USB to IDE/SATA adapter, and this adapter probably doesn't work properly.
    Another thing: I have some files on my external HDD because I don't have enough internal HDD space. Does EASEUS support compression? If not, I will try to come up with a solution for this.
     

    Attached Files:



Add New Comment

TechSpot Members
Login or sign up for free,
it takes about 30 seconds.
You may also...


Get complete access to the TechSpot community. Join thousands of technology enthusiasts that contribute and share knowledge in our forum. Get a private inbox, upload your own photo gallery and more.