System File Checker can't replace bad files

My friend's Win7 Home laptop can connect to their wifi network, but when I brought it to my house it can't connect to my wifi network. The laptop connects fine via Ethernet.

Further: nothing happens when I mouse over the Network icon in the system tray (when the laptop is at my house - I'm not sure what happens mousing over the icon on his network).

As if that weren't enough , when I go into the Manage Wireless Networks screen, nothing is there - nothing - no devices are listed. Normally at least a LAN and Wireless item are listed there.

There is no indication of anything wrong in Device Manager.

So I ran System File Checker and it found two bad files (autochk.exe and wlanmm.dll), but it also said that the source file was corrupted for each of them. I've attached the relevant entries from the sfcdetails.txt file that was generated.

The confusing part is, in the log file entries it says that the source file is corrupt, but at the end it then says "Verify and Repair Transaction completed. All files and registry keys listed in this transaction have been successfully repaired"

I'd appreciate any help you can offer. I'll be glad to provide any info you need to help me out.

Fist of all, schedule a disk check. chkdsk c: /f

I found wlanmm.dll.mui in 4 folders on my system:
- C:\Windows\winsxs\amd64_microsoft-windows-w..iamanager.resources_31bf3856ad364e35_6.1.7600.16385_en-us_2452b9550a34d471
- C:\Windows\System32\en-US
- C:\Windows\SysWOW64\en-US
- C:\Windows\winsxs\x86_microsoft-windows-w..iamanager.resources_31bf3856ad364e35_6.1.7600.16385_en-us_c8341dd151d7633b

Try to see where you find them on your computer and then replace the corrupted by the good one.

Thanks! I'll try that - hopefully tonight - and post back here.

Well, maybe this is due to another problem, but I'm not able to run chkdsk. I entered "Y" to have it run at next reboot, but when I reboot the computer just goes to the user logins and chkdsk never runs. I also tried to boot to safe mode with command prompt, but again the computer just booted to the user logins - albeit at a lower resolution due to safe mode.

I'll probably have to address that later, but that's not the point of this post.

I used "Everything" to search for wlanmm.dll.mui and it found the file in two places:

• C:\Windows\winsxs\amd64_microsoft-windows-w..iamanager.resources_31bf3856ad364e35_6.1.7600.16385_en_us_2452b9550a34d471
• C:\Windows\winsxs\x86_microsoft-windows-w..iamanager.resources_31bf3856ad364e35_6.1.7600.16385_en_us_c8341dd151d7633b

The amd64 one is 0KB and the x86 one is 4KB, so I'm guessing I'd use the x86 one. So do I simply backup the target file, copy over the x86 folder's file and reboot?

I would copy the x86 (4KB) to
- C:\Windows\winsxs\amd64_microsoft-windows-w..iamanager.resources_31bf3856ad364e35_6.1.7600.16385_en-us_2452b9550a34d471
- C:\Windows\System32\en-US
- C:\Windows\SysWOW64\en-US

For the Check disk, boot from the Win 7 installation disk, go to repair, open a CMD window and type chkdsk c: /f

It's been a while since I've had a chance to get back to this (life, friend wanted his laptop back for a bit, etc). I'd appreciate your (or someone's) continued help on this!

Megahertz07 said:

I would copy the x86 (4KB) to
- C:\Windows\winsxs\amd64_microsoft-windows-w..iamanager.resources_31bf3856ad364e35_6.1.7600.16385_en-us_2452b9550a34d471
- C:\Windows\System32\en-US
- C:\Windows\SysWOW64\en-US

Are you saying to copy the folder or just the file in it (I'm guessing the file, but I wanted to be crystal clear on that).

Also, you listed three locations. did you mean for me to copy the folder/file to all three of those locations?

Megahertz07 said:

For the Check disk, boot from the Win 7 installation disk, go to repair, open a CMD window and type chkdsk c: /f

This is a Toshiba Satellite laptop with a factory-installed OS, so I don't have access to the installation disk - unless there's an equivalent on the drive that I can force the computer to boot from or some such thing...

Copy the x86 (4KB) file to the folders
- C:\Windows\winsxs\amd64_microsoft-windows-w..iamanager.resources_31bf3856ad364e35_6.1.7600.16385_en-us_2452b9550a34d471
- C:\Windows\System32\en-US
- C:\Windows\SysWOW64\en-US

Don't you have any Win 7 installation disk to boot from and do a check disk?

Megahertz07 said:

Copy the x86 (4KB) file to the folders
- C:\Windows\winsxs\amd64_microsoft-windows-w..iamanager.resources_31bf3856ad364e35_6.1.7600.16385_en-us_2452b9550a34d471
- C:\Windows\System32\en-US
- C:\Windows\SysWOW64\en-US

Don't you have any Win 7 installation disk to boot from and do a check disk?

Thanks for clarifying. I figured that was what you meant, but when I'm dealing with system files I want to be crystal clear on what to do - especially with someone else's computer!

No, unfortunately I don't have a Win 7 install disk available.

Download the down loader Microsoft Windows and Office ISO Download Tool
With the down loader, download any version of Win 7 64.
It can be used to repair any win 7 64 version.
To use the disk to install any win 7 64 version, rename \sources\ei.cfg to \sources\ei.cfg.orig
When you go to install, it will ask what brand of Win 7 you want to install.

I'm downloading the loader right now. While waiting for that I tried copying the file to the folders as instructed above. I tried creating a copy of the 0KB wlanmm.dll.mui file, but I got a permissions message so I copied the file's folder to the desktop. Having done that, I tried copying the x86 folder's file to the amd64 folder to overwrite the 0KB file, but I'm getting the message "You need permission to perform this action". I have admin rights on my login. I don't recall any sort of UAC feature on Win7 (although it's been an awfully long time...)

I tried copying the file via an elevated cmd using the "copy" command, but got an Access is denied message. That's the extent of my knowledge on that. I'm sure there must be a way to force the copy/overwrite.

But as I'm downloading the loader I'm wondering if that's even necessary because wouldn't running the Win 7 installer fix the issue anyway?