iPhone recognised by iTunes but not by windows

[MooGuru]

Greetings all, and many thanks in advance for any help you can give on this problem. Wasn't sure where to post this, if its in the wrong spot just shout at me and I'll move it to the correct forum lol.

Issue: iPhone 5 does not show up on Windows 7 64bit Home Premium laptop so photos can't be imported. iTunes recognises it and will sync, but the autoplay "import pictures and videos" does not work. The iPhone does not show up as a device under "my computer" or in "control panel / autorun" but does show up in the device manager (when iPhone is attached, there are 2 entries to the device manager "Portable Device / iPhone" and "Universal Serial Bus controllers / Apple Mobile Device USB Driver").

Attempted solutions:

• uninstall iTunes and reinstalled, cleaned all references and folders between uninstall and reinstall - problem still exists
• tried with a different laptop (Windows 7 Professional 64bit) - worked fine and photos were imported to that laptop as expected (so there IS a backup of them available but this is a work laptop and ideally would like the photos to be backed up and restored to the home laptop) so the issue is not with the cable or iTunes or the device (I think :huh: )
• reinstalling the driver for "Portable Device / iPhone" - produced an error message "Windows found a driver for your device but encountered an error while attempting to install it. MTB USB Device. The dependency service or group failed to start."
• googling the above error led me to http://www.sevenforums.com/hardware...iver-software-not-successfully-installed.html which led me to check " start / msinfo32 / components / problem devices" where the following was listed "User Mode Driver Frameworks Platform Driver ROOT\LEGACY_WUDFPF\0000 This device is not present, is not working properly, or does not have all its drivers installed."

On the basis of that I decided to come here and pick the brains of people who know what they're doing . As I said, the photos have now been backed up, so it isn't an immediate fix that I require, but I would like to solve this problem so I don't have to backup then copy onto pen drive and transfer all over again!

Any assistance will be much appreciated, thank you in advance.

 

[ThrashZone]

Hi and welcome to SevenForums,
Not sure about the driver issue but I've always found it simper to access the device directly and not use autoplay,
Click start and computer,
If the iphone is listed simply click or right click open,
Keep doing so until you get to the dcim folder where your .mov and .img files are located and copy and paste them where you want to
Someone else may have some input for the driver,
Cheers.

 

[MooGuru]

Hi, thanks for the reply and the advice

Unfortunately, due to the driver issue, its not listed as a removable device under "My Computer" it is only recognized by iTunes itself.

Still not solved, and still looking for an answer! Thanks again

 

[ThrashZone]

Hi,
See if this finds anything if you haven't already,
http://www.sevenforums.com/tutorials/1538-sfc-scannow-command-system-file-checker.html

 

[MooGuru]

Update on this:

Checked device manager again, and viewed hidden devices: gave an error for the device "User Mode Driver Frameworks Platform Driver" - This device is not present, is not working properly, or does not have all its drivers installed. (Code 24)

Following google advice, I checked the services in Computer Management: the service I was directed to look for (Windows Driver Foundation - User-mode Driver Framework) was not started, and right clicking and selecting Start gave the following error message - Error 1068 The dependency service or group failed to start

Good old google led me to check whether WudfPf.sys file exists in the %WinDir%\system32\drivers folder - it doesn't so I'm guessing that's what the issue is but I'm not comfortable downloading alleged repairs or installs from the internet and Microsoft doesn't appear to offer any support on this (that I could find).

I have now run (as suggested by ThrashZone - thank you!) sfc /scannow and it identified but could not repair the problem. I get the following text part way through the verification process:
2015-03-31 13:31:22, Info CSI 000000a8 [SR] Verifying 100 (0x0000000000000064) components
2015-03-31 13:31:22, Info CSI 000000a9 [SR] Beginning Verify and Repair transaction
2015-03-31 13:31:27, Info CSI 000000ac [SR] Cannot verify component files for Microsoft-Windows-DriverFrameworks-UserMode.Resources, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2015-03-31 13:31:32, Info CSI 000000ae [SR] Cannot repair member file [l:20{10}]"WUDFPf.sys" of Microsoft-Windows-DriverFrameworks-UserMode, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-31 13:31:32, Info CSI 000000b0 [SR] Cannot repair member file [l:80{40}]"MsftWdf_User_01_11_00_Inbox_Critical.Wdf" of Microsoft-Windows-DriverFrameworks-UserMode, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-31 13:31:36, Info CSI 000000b2 [SR] Cannot repair member file [l:20{10}]"WUDFPf.sys" of Microsoft-Windows-DriverFrameworks-UserMode, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-31 13:31:36, Info CSI 000000b3 [SR] This component was referenced by [l:156{78}]"Package_1_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.2685813-2_neutral_GDR"
2015-03-31 13:31:36, Info CSI 000000b5 [SR] Cannot repair member file [l:80{40}]"MsftWdf_User_01_11_00_Inbox_Critical.Wdf" of Microsoft-Windows-DriverFrameworks-UserMode, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-31 13:31:36, Info CSI 000000b6 [SR] This component was referenced by [l:156{78}]"Package_1_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.2685813-2_neutral_GDR"
2015-03-31 13:31:36, Info CSI 000000b9 [SR] Could not reproject corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\System32\drivers"\[l:20{10}]"WUDFPf.sys"; source file in store is also corrupted
2015-03-31 13:31:36, Info CSI 000000bc [SR] Could not reproject corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\System32\drivers"\[l:80{40}]"MsftWdf_User_01_11_00_Inbox_Critical.Wdf"; source file in store is also corrupted
2015-03-31 13:31:36, Info CSI 000000bf [SR] Recovered manifest from backup for Microsoft-Windows-DriverFrameworks-UserMode.Resources, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-03-31 13:31:37, Info CSI 000000c4 [SR] Verify complete

And the following text and the end, during the repair process:
2015-03-31 13:59:38, Info CSI 00000349 [SR] Repairing 2 components
2015-03-31 13:59:38, Info CSI 0000034a [SR] Beginning Verify and Repair transaction
2015-03-31 13:59:38, Info CSI 0000034c [SR] Cannot repair member file [l:20{10}]"WUDFPf.sys" of Microsoft-Windows-DriverFrameworks-UserMode, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-31 13:59:38, Info CSI 0000034e [SR] Cannot repair member file [l:80{40}]"MsftWdf_User_01_11_00_Inbox_Critical.Wdf" of Microsoft-Windows-DriverFrameworks-UserMode, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-31 13:59:38, Info CSI 00000351 [SR] Cannot verify component files for Microsoft-Windows-DriverFrameworks-UserMode.Resources, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral, manifest is damaged (TRUE)
2015-03-31 13:59:39, Info CSI 00000354 [SR] Recovered manifest from backup for Microsoft-Windows-DriverFrameworks-UserMode.Resources, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture = [l:10{5}]"en-US", VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral
2015-03-31 13:59:39, Info CSI 00000356 [SR] Cannot repair member file [l:20{10}]"WUDFPf.sys" of Microsoft-Windows-DriverFrameworks-UserMode, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-31 13:59:39, Info CSI 00000357 [SR] This component was referenced by [l:156{78}]"Package_1_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.2685813-2_neutral_GDR"
2015-03-31 13:59:39, Info CSI 00000359 [SR] Cannot repair member file [l:80{40}]"MsftWdf_User_01_11_00_Inbox_Critical.Wdf" of Microsoft-Windows-DriverFrameworks-UserMode, Version = 6.1.7601.17803, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2015-03-31 13:59:39, Info CSI 0000035a [SR] This component was referenced by [l:156{78}]"Package_1_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.2685813-2_neutral_GDR"
2015-03-31 13:59:39, Info CSI 0000035d [SR] Could not reproject corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\System32\drivers"\[l:20{10}]"WUDFPf.sys"; source file in store is also corrupted
2015-03-31 13:59:39, Info CSI 00000360 [SR] Could not reproject corrupted file [ml:520{260},l:62{31}]"\??\C:\Windows\System32\drivers"\[l:80{40}]"MsftWdf_User_01_11_00_Inbox_Critical.Wdf"; source file in store is also corrupted
2015-03-31 13:59:39, Info CSI 00000362 [SR] Repair complete
2015-03-31 13:59:47, Info CSI 00000367 [SR] Committing transaction
2015-03-31 13:59:48, Info CSI 0000036b [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired

The sfc scan gave me the following message on completion:
Windows Resource Protection found corrupt files but was unable to fix some of them

So ... now what? lol. There is no windows disk (pre-installed) and no backup was taken on first launch (daughter's laptop, since when do kids listen to parents?), and the above says that the backup version sfc repairs from was also corrupt.

Microsoft says "manually replace the corrupted file with a known good copy of the file." - can this be from any Windows PC, or any Windows 7 PC, regardless of version? Or does it have to be another Windows 7 Home Premium SP1 system that I get the good files from? Or is there somewhere safe I can download them from? And do I just replace the corrupt ones with copy and paste, or is there a process I'll need to go through to get the good files working correctly?

 

[ThrashZone]

Thank you I asked for help for you but traditionally running sfc/scannow 3 times in a row might fix some issues,
Give it a try and see if not uninstall iTunes and all that comes with it,
Cheers and stand by.

 

[MooGuru]

Thanks ThrashZone, 3rd time didn't work like a charm ;(

I've now run SFC twice in normal mode and once in safe mode, I'm attaching the log text file for whichever hero wants to point me in the direction of a solution!

On the plus side, my son has a duplicate laptop (same manufacturer, same OS) and SFC is clean on his one, so I do potentially have a source for non-corrupted files, as long as the files in question are standard windows issue I just need someone to tell me what, where and how.

 

[NoelDP]

SFC managed to fix one problem it found - but couldn't fix a couple of others.

Before we attempt to fix those,
Please follow the Windows Update Posting Instructions and post the requested data

If the file is too large (8MB compressed), remove the older CBSPersist cab files until the final file is below the limit - you can always post them separately after zipping them. (the forum doesn't allow the upload of bare CAB files, for a number of reasons)

 

[MooGuru]

Many thanks Noel,

I've done as instructed, and have attached the CBS zipped file - unfortunately one of the CBSpersist files was extremely big, and even separated from the rest and zipped, the file size is still over 11mb.

So, the attachment "CBS(2).zip" does not contain the most recent CbsPersist file.

This link should take you to a folder on my dropbox which contains the complete exported and compressed CBS folder ("CBS.zip" which includes the big, recent file). https://www.dropbox.com/sh/poi82xhkctm4iko/AAA-KdlFfIAxwPjYI2z0gXYMa?dl=0

Thanks again

 

[NoelDP]

Here's the error list from CheckSUR -

Summary:
Seconds executed: 4206
 Found 18 errors
  CSI Manifest All Zeros Total count: 1
  CSI Manifest and S256H Do Not Match Total count: 2
  CSI Manifest Failed Catalog Check Total count: 1
  CBS MUM Corrupt Total count: 7
  CBS Catalog Corrupt Total count: 7
Unavailable repair files:
 winsxs\manifests\amd64_microsoft-windows-d..-usermode.resources_31bf3856ad364e35_6.1.7601.17803_en-us_251461586e43c0e3.manifest
 winsxs\manifests\amd64_microsoft-windows-d..-usermode.resources_31bf3856ad364e35_6.1.7600.21203_en-us_23b7793f8a3b2803.manifest
 winsxs\manifests\amd64_microsoft-windows-d..-usermode.resources_31bf3856ad364e35_6.1.7600.17013_en-us_23230aa27125a703.manifest
 winsxs\manifests\amd64_microsoft-windows-d..-usermode.resources_31bf3856ad364e35_6.1.7601.22004_en-us_259ed68f8760ad46.manifest
 servicing\packages\Package_1_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
 servicing\packages\Package_1_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
 servicing\packages\Package_75_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
 servicing\packages\Package_75_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
 servicing\packages\Package_82_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
 servicing\packages\Package_82_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
 servicing\packages\Package_8_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
 servicing\packages\Package_8_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
 servicing\packages\Package_for_KB2685813_RTM~31bf3856ad364e35~amd64~~6.1.1.11.mum
 servicing\packages\Package_for_KB2685813_RTM~31bf3856ad364e35~amd64~~6.1.1.11.mum
 servicing\packages\Package_for_KB2685813_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum
 servicing\packages\Package_for_KB2685813_SP1~31bf3856ad364e35~amd64~~6.1.1.11.mum
 servicing\packages\Package_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum
 servicing\packages\Package_for_KB2685813~31bf3856ad364e35~amd64~~6.1.1.11.mum

I'll post a fix protocol when I can find the time - probably tomorrow before I get to clear the backlog

 

[NoelDP]

I've uploaded a file - mguaa.zip - to my OneDrive at Noel's OneDrive
Please download and save it.
Right-click on the downloaded file, and select Extract all…
Extract to the default location - which will create a new folder mguaa in the same place.
Open this folder - there should be two folders inside it (Manifests, and Packages)

Copy the content of the Packages folder to the folder
C:\Windows\Temp\CheckSur\Servicing\Packages

And the content of the manifests folder (.manifest files) into this folder:

C:\Windows\Temp\CheckSur\Winsxs\Manifests

Now run the CheckSUR tool again (it may take a while)

Post the new CheckSUR.log file, and the CheckSUR.persist.log file.

 

[MooGuru]

Thanks Noel,

Please find attached a zip copy of all the files modified today in my Logs/CBS folder.