disabling intel pro 100/1000 pl network connection

[abb]

i have a new x60s 17044du and I'm having a problem disabling the intel lan connection. At times, i am unable to disable the intel network lan in the network connections menus and it displays a message "error disabling connection"...something due to plug in play or another system account using the device (although the comp only has one account, mine which is the administrator).

When this happens, the only way I can disable the device is through the device manager or through the thinkpad configuration. However, at random times when I reboot, the intel pro 100/1000pl pl network lan automatically enables itself again. Everything seems to be working fine since my intel abg wireless card functions well. however, the annoying disconnected icon in the task bar representing the intel LAN network which I can't remove is an eyesore.

Has anybody experienced a similar problem? Is this a software issue? Ive reformated with the factory preload multiple times but the same issue arises. Ive had a t42 in the past and ive had no problem disabling the lan since is use Wlan the majority of the time.

any help would be appreciated.

[sugo]

Have you tried uninstalling Access Connections to see if it makes any difference?

[abb]

Have you tried uninstalling Access Connections to see if it makes any difference?

sugo. yes, i have tried uninstalling access connections and i still have the same problem. does anybody else have any suggestions?

does this have to do with the lan and wlan cards both being intel and thus have to be enabled at the same time?

my 30 days is coming to end so i wanted to make sure this is not a hardware problem.

[Kyocera]

have you tried reinstalling to factory, usually tech support asks or suggests trying that, if it's within the 30 days you need to get that squared away quick.

[JML]

Took me hours to find the cause and the solution.

The problem is that Lenovo uses unsigned drivers for the wireless and wired network hardware, and they're installed EITHER by using the Lenovo update or Windows update process. For me, it was caused by a Rescue & Recovery rebuild.

The unsigned drivers trigger a Windows glitch, described in MS article #822798, foud at http://support.microsoft.com/kb/822798. The solution for me was renaming the catroot2 folder in System32 to "oldcatroot" and rebooting.