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)