4320t Wireless Stops Working after 90 days

On this 4320t, I've found that the wireless will stop working after 90 days for some reason.

With System32 folder in FBWF exclusion list, wireless works fine no matter what.

With System32 not excluded from FBWF, and FBWF Enabled, going forward at least 90 days on the local Windows date and rebooting, wireless stops working (no wireless networks are in range, and the "Wireless Networks" tab disappears from the Wireless Connection Properties).
 
I can fix it by Disabling the FBWF, rebooting, uninstall/reinstall wireless broadcom device, reboot, re-enable FBWF.
However, if I were to go to the same laptop I just fixed, disable the FBWF again, reboot, re-enable the FBWF, reboot, then change the date forward at least 90 days, the wireless would stop again.
 
I can re-create this on a new imaged laptop.

This sounds very odd, any theories? I'd hate to have to leave open the system32 on an XP embedded 4320t laptop, since that may pose a security risk. But it sure is getting annoying having to fix all these wireless issues exactly 90 days later after a laptop was re-imaged.


Device: Broadcom 43224AG 802.11a/b/g/draft-n Wi-Fi Adapter
Current Driver: BCM43XX Broadcom 802.11 Network Adapter Driver
Driver version: 5.60.350.6 (3/22/2010)
C:\Windows\system32\drivers\bcmwl5.sys¿
garryshapeAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

gheistCommented:
Anything in system logs? Why do you think wireless driver is at fault?
0
garryshapeAuthor Commented:
Unfortunately nothing shows up in the logs at all. It may be turned off in the Group Policy that came from HP or something.
I don't know if it's the wireless driver's fault. But the Wired driver for LAN doesn't have this issue.
0
garryshapeAuthor Commented:
An MS parter from MSDN advised me to try adding to the exception "C:\Windows\System32\config\systemprofile\Application Data\Microsoft\SystemCertificates".

I will try this tomorrow and report my results.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

gheistCommented:
I would try getting around without rebooting or reinstalling. Say http://support.microsoft.com/kb/311272/en-us

Your drivers are latest from HP for your model:
http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?cc=uk&destPage=softwareDownloadIndex&jumpid=reg_r1002_benl&lc=en&softwareitem=pv-91023-1&tmp_docname=

Should the diagnosis point to them you are eligible for a support call (mail/web/phone)

Should that fail:
http://www8.hp.com/us/en/hp-search/search-results.html?cc=us&lang=en&qt=%22broadcom+wireless+lan+driver%22&cat=ALL_RESULTS&pgn=2&initial_view=false (like 100 driver packs for XP/2000)

eg one more recent:

http://h10025.www1.hp.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-93103-1&cc=us&dlc=en&lc=en&jumpid=reg_r1002_usen

If you find no way you can try Others: Lenovo/DELL makes wireless cards, Apple has some broadcom drivers in BootCamp too.

0
garryshapeAuthor Commented:
Know of a tool I can use to compare folders/files such as the system32 folder?
I want to compare this folder to when the write filter's off versus write filter being on.
0
gheistCommented:
would be nice if you figure this out yourself or with hand holding from HP. FBWF is not a general purpose software, and i would say 1/1000000 broadcom network card users use it (or any other filesystem filter for that matter)
0
garryshapeAuthor Commented:
Yeah HP's been anything but helpful during this troubleshooting process.

It's not the  C:\Windows\System32\CONFIG or C:\Windows\System32\DRIVERS folders. Tried excluding those from write filter but problem comes back.
0
garryshapeAuthor Commented:
I think I've narrowed it to excluding these two:

•      C:\Windows\System32\bcmwlcoi.dll
•      C:\Windows\System32\Drivers\bcmwl5.sys

Still testing.
0
gheistCommented:
-wlcoi- is installer for broadcom connection manager. inless you use that it is not necessary

you need to find inf or msi file which installed it and UNINSTALL
0
garryshapeAuthor Commented:
NOPE.
Excluding those two files after a re-image then going forward 90 days still causes wireless to drop.

However, excluding the whole System32 folder and going forward 90 days, wireless continues to work.
0
gheistCommented:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Wlansvc\Parameters\OneXAuthenticator

i see other DLLs being loaded for "supplicant" authentications....
Maybe they have bug inside... Or simply write some calibration data to somewhere...
0
gheistCommented:
http://technet.microsoft.com/nl-be/sysinternals/bb896646 i think it has same file based view (or check around the site - maybe i picked the wrong tool)
0
garryshapeAuthor Commented:
Using WinMerge to compare a dir /s > report.txt of the c:\windows\system32 folder, one report being in a "wireless working" state, and the other being in a "wireless NOT working" state, I see no differences in the files/folders that would indicate which file/folder needs to be excluded from the File Based Write Filter.

I bet it simply just needs access to the system32 folder.
0
gheistCommented:
Maybe something gets defragmented on schedule or enough of AV updates etc....
http://msdn.microsoft.com/en-US/library/aa940931%28v=WinEmbedded.5%29.aspx
0
garryshapeAuthor Commented:
Found the fix. From someone at MSDN forum:

Try to set the option in Windows Explorer->Tools->Folder Options->View->”Show hidden files” and folders and uncheck “Hide protected operating system files” first.
Try to add the folder C: \Windows\System32\Microsoft\Protect\S-1-5-18\User to the exclusion list next.
The issue is related to “Windows Data Protection”.
http://support.microsoft.com/default.aspx?scid=kb;EN-US;309408
http://msdn.microsoft.com/en-us/library/ms995355.aspx
“DPAPI helps protect confidential information by using value data derived from a pseudo-random 512-bit number named a master key. Windows Server 2003 domain controllers use a 2048-bit RSA key, but only when the domain is running in domain functional level 2 or Windows Server 2003 mode. Each user account has one or more randomly generated master keys. The number of master keys depends on the age of the user's profile. Master keys are renewed at regular intervals. By default, this value is every 90 days.”

---Sergey

In my case, I've just added the "Microsoft" folder in System32 to Exclusions, and that has fixed it.

Am shocked this wouldn't be excluded by default.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
garryshapeAuthor Commented:
This was found.
0
gheistCommented:
best is to report to vendor. that may give you some bonus points approaching them next time.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.