Ошибка 4001 служба автонастройки беспроводной сети остановлена успешно

• Remove From My Forums

All replies

• Is there a legitimate reason for this?   I keep getting this in event viewer also.  Frustrating….looks like there would be a «fix» for it. 
   :»

• Perhaps the reason it is there is this is the error I get just before my system crashes!

• Don’t you guys get it?  In this day and time, most IT people, engineers, politicians, etc., etc. (and I did say most, not all) forget steps, don’t double check what they do, are too interested in what «they want» (and they shove that down our
  throat, and just don’t do what «we» want, and that is provide us with a trouble free system.  All of this «social crap» (which is guess does provide the ability to do what I’m doing) is another way for them to eventually make more money buy us buying
  more crap.  They will NEVER admit they made a mistake.  They will tell you how to «work around», «adapt», etc, etc.  Do i sound frustrated?  Yes, I’m sick of this junk.  Windows 95 was faster than Windows 7.  Granted, Windows
  95 never had all the «bells and whistles» that we have now, but what has all of that done for us?  Oh well, they probable won’t post this.  If they do, get ready for Windows 8, Windows 9, Windows 9tt, so on and so forth and be prepared for them to
  woryy you to death till you buy it.  Oh, you will have to because all of this that halfway works now, won’t work at all then.

• This happens when your wireless network adapter is configured to turn off after a period of inactivity to save power.

  

  It says successful because: It was configured to do so, and it did.
  It pops as a warning because: This will result in network dis-connectivity, so if the user does not want it to be this way, he should change the setting.

  That’s not stupid, that’s thoughtful on the Microsoft developer’s part for power saving. It’s just that we don’t see it the way it was meant to be..
  Hope it helps!

  ---

  Kunal D Mehta — a Windows Server Enthusiast.

• Guess what- That doesn’t work. I tried it and I still get the warning.

• Me too. It doesn’t work and still get the warning

• I also tried the solution posted above from ServerBaba and it doesn’t work for me.  I still get the  «Event ID 4001, WLAN AutoConfig service has successfully stopped» as a warning in my system event log. If the task completed successfully
  then why is it considered a «warning» and not «information.  Please Microsoft, help us resolve this issue. 

• Greetings,

  I too was receiving this error also, although my setup may be different than the users that have posted here.

  I use my Ethernet NIC most of the time and keep my WLAN as a redundant backup in case the wired side drops. I was logging this error whether the adapter was enabled or not, since the service was still active in the Automatic mode.

  Upon every boot, I was logging EventId 4001. I was able to keep the WLAN network adapter enabled and eliminate the error by simply switching the WLAN service setting from Automatic to Manual.

  If you are using the wireless connection and NOT the Ethernet NIC, I am not sure if this will also work for you (as I have not tried it), but it did solve my error logging issue of the EventId 4001 in my situation, which was annoying me much in the same
  way as the others here have articulated, since there really is no need for a warning at all IMHO.

  I am assuming that upon boot, the wireless service is called to respond ( in the automatic mode), and if there is not active connection, the service then will generate the message when the service is called to stop & listen for another call.

  Hope this is of some help to the group, and in either case I am no longer logging the EventId 4001 so it worked for me.

  Adminstrative Tools>Services>WLAN Auto Config—> Set to Manual.

  Cheers!

  • Edited by

    Friday, March 30, 2012 1:47 PM

• This solution is also a bust. I use wireless exclusively and had the service set to Manual.The warning continues.

• Hi server baba. I only tried one thing. I went into services and stopped the Wlan (wireless lan) service and then restarted it.

  The stop action left a warning in the event log with id 4001 and the start action left an information entry in the system event log with id 4000.

  I think a warning is unnecessary in this case so the problem though minor is real. 

• Just to complete the diagnosis, I stopped and restarted the workstation service which is also a fairly important network service.

  No warning event ids were issued, only information type events. I rest my case. This is indeed a problem

• I too have been experience this error. I only use WLAN and I went into the Properties for the service and discovered after it fails twice it doesn’t restart. This meant I lost connectivity to Network.

  The connectivity returns after a reboot and when it fails/stops twice, it won’t restart.

  

  The reset count default is zero — > now 2

  After subsequent failures, is now «Restart The Service»

  Applied changes Clicked «OK» and waiting to see if the Network lockout s overcome.

• I turned off the power feature as suggested and still get the warning…Lenovo t60..win 7 build 7601 sp1…what’s up with this?

• I have a solution. It’s not pretty!

  In the process I lost some user data (recent docs) + the ability to create recent docs… I ticked and unticked the relevant checkboxes, restarted, and the ‘recent programs’ list began to re-populate.

  There are some people who are having issues with auto-reconnection failing — this is not for you.

  This is for people that don’t like to see information events arguably incorrectly
  identified as warnings.

  The fix?

  Computer mgmt has the data collector sets (under performance). 

  Under Event Trace Sessions you’ll find EventLog-System, containing all the event log ‘system’ sources (I think).

  You won’t have permission to change this as an admin. You need to be the sys. I achieved this by using the sticky keys event-handler to launch taskmgr (I was testing alternatives to diskpart scripts to load a VHD @ startup)

  REG ADD «HKLMSOFTWAREMicrosoftWindows NTCurrentVersionImage File Execution Optionssethc.exe» /v Debugger /t REG_SZ /d «c:windowstaskmgr.exe»

  running that at a cmd prompt will allow you to 5-tap shift to load taskmgr- as SYSTEM (god).

  from here run compmgmt.msc, stop eventlogsys, remove the wlan-autoconfig source, et voile.

• Bought a laptop new. 2008. Vista SP 1. April. Event Viewer reported factory crash at OS install. March…WELCOME..

• Nicely done!
  It seems after a year, that little feature/bug is still present.

• Remove From My Forums

Все ответы

• Is there a legitimate reason for this?   I keep getting this in event viewer also.  Frustrating….looks like there would be a «fix» for it. 
   :»

• Perhaps the reason it is there is this is the error I get just before my system crashes!

• Don’t you guys get it?  In this day and time, most IT people, engineers, politicians, etc., etc. (and I did say most, not all) forget steps, don’t double check what they do, are too interested in what «they want» (and they shove that down our
  throat, and just don’t do what «we» want, and that is provide us with a trouble free system.  All of this «social crap» (which is guess does provide the ability to do what I’m doing) is another way for them to eventually make more money buy us buying
  more crap.  They will NEVER admit they made a mistake.  They will tell you how to «work around», «adapt», etc, etc.  Do i sound frustrated?  Yes, I’m sick of this junk.  Windows 95 was faster than Windows 7.  Granted, Windows
  95 never had all the «bells and whistles» that we have now, but what has all of that done for us?  Oh well, they probable won’t post this.  If they do, get ready for Windows 8, Windows 9, Windows 9tt, so on and so forth and be prepared for them to
  woryy you to death till you buy it.  Oh, you will have to because all of this that halfway works now, won’t work at all then.

• This happens when your wireless network adapter is configured to turn off after a period of inactivity to save power.

  

  It says successful because: It was configured to do so, and it did.
  It pops as a warning because: This will result in network dis-connectivity, so if the user does not want it to be this way, he should change the setting.

  That’s not stupid, that’s thoughtful on the Microsoft developer’s part for power saving. It’s just that we don’t see it the way it was meant to be..
  Hope it helps!

  ---

  Kunal D Mehta — a Windows Server Enthusiast.

• Guess what- That doesn’t work. I tried it and I still get the warning.

• Me too. It doesn’t work and still get the warning

• I also tried the solution posted above from ServerBaba and it doesn’t work for me.  I still get the  «Event ID 4001, WLAN AutoConfig service has successfully stopped» as a warning in my system event log. If the task completed successfully
  then why is it considered a «warning» and not «information.  Please Microsoft, help us resolve this issue. 

• Greetings,

  I too was receiving this error also, although my setup may be different than the users that have posted here.

  I use my Ethernet NIC most of the time and keep my WLAN as a redundant backup in case the wired side drops. I was logging this error whether the adapter was enabled or not, since the service was still active in the Automatic mode.

  Upon every boot, I was logging EventId 4001. I was able to keep the WLAN network adapter enabled and eliminate the error by simply switching the WLAN service setting from Automatic to Manual.

  If you are using the wireless connection and NOT the Ethernet NIC, I am not sure if this will also work for you (as I have not tried it), but it did solve my error logging issue of the EventId 4001 in my situation, which was annoying me much in the same
  way as the others here have articulated, since there really is no need for a warning at all IMHO.

  I am assuming that upon boot, the wireless service is called to respond ( in the automatic mode), and if there is not active connection, the service then will generate the message when the service is called to stop & listen for another call.

  Hope this is of some help to the group, and in either case I am no longer logging the EventId 4001 so it worked for me.

  Adminstrative Tools>Services>WLAN Auto Config—> Set to Manual.

  Cheers!

  • Изменено

    30 марта 2012 г. 13:47

• This solution is also a bust. I use wireless exclusively and had the service set to Manual.The warning continues.

• Hi server baba. I only tried one thing. I went into services and stopped the Wlan (wireless lan) service and then restarted it.

  The stop action left a warning in the event log with id 4001 and the start action left an information entry in the system event log with id 4000.

  I think a warning is unnecessary in this case so the problem though minor is real. 

• Just to complete the diagnosis, I stopped and restarted the workstation service which is also a fairly important network service.

  No warning event ids were issued, only information type events. I rest my case. This is indeed a problem

• I too have been experience this error. I only use WLAN and I went into the Properties for the service and discovered after it fails twice it doesn’t restart. This meant I lost connectivity to Network.

  The connectivity returns after a reboot and when it fails/stops twice, it won’t restart.

  

  The reset count default is zero — > now 2

  After subsequent failures, is now «Restart The Service»

  Applied changes Clicked «OK» and waiting to see if the Network lockout s overcome.

• I turned off the power feature as suggested and still get the warning…Lenovo t60..win 7 build 7601 sp1…what’s up with this?

• I have a solution. It’s not pretty!

  In the process I lost some user data (recent docs) + the ability to create recent docs… I ticked and unticked the relevant checkboxes, restarted, and the ‘recent programs’ list began to re-populate.

  There are some people who are having issues with auto-reconnection failing — this is not for you.

  This is for people that don’t like to see information events arguably incorrectly
  identified as warnings.

  The fix?

  Computer mgmt has the data collector sets (under performance). 

  Under Event Trace Sessions you’ll find EventLog-System, containing all the event log ‘system’ sources (I think).

  You won’t have permission to change this as an admin. You need to be the sys. I achieved this by using the sticky keys event-handler to launch taskmgr (I was testing alternatives to diskpart scripts to load a VHD @ startup)

  REG ADD «HKLMSOFTWAREMicrosoftWindows NTCurrentVersionImage File Execution Optionssethc.exe» /v Debugger /t REG_SZ /d «c:windowstaskmgr.exe»

  running that at a cmd prompt will allow you to 5-tap shift to load taskmgr- as SYSTEM (god).

  from here run compmgmt.msc, stop eventlogsys, remove the wlan-autoconfig source, et voile.

• Bought a laptop new. 2008. Vista SP 1. April. Event Viewer reported factory crash at OS install. March…WELCOME..

• Nicely done!
  It seems after a year, that little feature/bug is still present.

Содержание

• Способ 1: Использование средства автоматического исправления неполадок
• Способ 2: Ручное включение Wi-Fi на компьютере или ноутбуке
• Способ 3: Включение сетевого адаптера
• Способ 4: Ручной запуск службы
• Способ 5: Обновление сетевых настроек
• Способ 6: Сброс сетевых настроек
• Способ 7: Проверка конфигурации системы
• Способ 8: Проверка связанных служб
• Способ 9: Установка последней версии сетевого драйвера
• Вопросы и ответы