- Joined
- Aug 14, 2015
- Messages
- 4
- Reaction score
- 0
Well, it was an 'interesting' week. I did an upgrade from Windows 7 Pro into Win 10 Pro.
Asus motherboard, Intel 82579V Gigabit wired Ethernet connection.
So, here is a list, a pathetic Microsoft support is unable to neither understand nor comprehend less to offer any ideas of what to do with.
1. Power management plain broken. No activities initiate for power modes change, no screensaver activation, no power down monitors upon pre-set timeout, zilch.
2. A MAJOR issue that I think I saw multiple times in other posts that affects most of the system.
Windows 10 has a completely broken proxy auto detection.
It is invisible and does not affect internet browsing but about of a half of a system processes is then plain broken due to that bug. Those processes cannot communicate.
It means but not limited to - XBOX application will not log you in, in the settings 'accounts' section you cannot login into Microsoft account claiming 'you are not connected to Internet', Windows Store is not working, Office 365 cannot connect to servers and neither create account nor get mail (while internal Mail client in Win10 works fine with same Office365 account), etc.
Naturally, your network status is shown happily connected to that Internet, no troubleshooters detect anything, there are no visible signs of any issues, it is all hidden into Win10 guts.
I was hit by it initially when I installed Office 365 and Outlook 2013 was unable to connect to our corporate exchange server, for no obvious reason.
At the same time, Windows update would not be able to work popping up incomprehensible error 0x80240438.
A first partial solution is to proceed to
Control Panel\All Control Panel Items\Network and Sharing Center
then click at 'internet option' in the lower left corner, go to 'connections' tab and into 'lan settings' and uncheck this dreaded checkmark in the 'autodetect' proxy feature. that will make most applications happy. It gets set 'checked' by default.
BUT NOT THE CORE WINDOWS BITS SERVICE!!! Developers worked long and hard to make this system unfixable.
All default jobs for downloads are submitted into BITS with proxy set to 'AUTODETECT'. That efficiently results in your windows store application unable to download anything, in you windows update unable to download anything - it does not error out, of course, it just starts download and sits stuck in there forever at 0%. To see what is going on you need to use bitsadmin tool from the command prompt ran under admin privileges and look at the list of tasks -
bitsadmin /list/ allusers
or read this
http://answers.microsoft.com/en-us/...e/17f48b91-c12c-41de-8c3a-63954cd40639?auth=1
and this
http://blogs.technet.com/b/networki...-to-test-the-bits-client-on-your-machine.aspx
In the test above you can see if you submit a job with NO_PROXY specified - it works like a charm.
but if you do that
Bitsadmin /setproxysettings bitstest preconfig
or that
Bitsadmin /setproxysettings bitstest autodetect
- you get same exact situation with a bits job hanging forever.
If you run
bitsadmin.exe /Util /GetIEProxy LocalSystem
and then
bitsadmin.exe /info {--job_id--} /verbose
you will see that windows keeps posting all jobs into BITS enforcing AUTODETECT as a default ignoring your settings.
you can use
bitsadmin.exe /Util /SetIEProxy LocalSystem NO_PROXY
- it does set it correctly, but, you have guessed right - Windows 10 does not give a damn what it is you set up and keeps creating jobs with AUTODETECT that never works.
WORKAROUNDS
as ridiculous as Microsoft is, workaround is also of a same kind. If you have a work VPN - Cisco or anything - there is a 90% chance that if you connect to VPN over same network adapter - it will work fine - that is my solution.
Other solution is to create an actual d@mn proxy in your proxy-less network and configure it manually into BITS using same bitsadmin, and with some luck it may start to work.
On my machine it sometimes starts to work and download updates after I reset winsock and tcp4 but it 'fixes' itself overnight and next day it does not work again.
NOTHING of what I explained above is within understanding of this Indian support that may call you if you open a ticket, they act like they hear words BITSADMIN for a first time in their call center lives, that may be indeed a true fact.
Still, it is very annoying and very frustrating. And took me some time to dig to the root of it.
I am still unable to find why original proxy autodetect is broken - all Intel drivers were tested, router udated, DHCP removed from router and moved into Linux DHCPD process and back, fixed IP address was set on the interface, IPV6 added and removed from both Windows and router - nothing so far did any difference to make autodetect work.
Where it works is our corporate network where there is a hardware proxy solution and DHCP serviced from a corporate switch.
Asus motherboard, Intel 82579V Gigabit wired Ethernet connection.
So, here is a list, a pathetic Microsoft support is unable to neither understand nor comprehend less to offer any ideas of what to do with.
1. Power management plain broken. No activities initiate for power modes change, no screensaver activation, no power down monitors upon pre-set timeout, zilch.
2. A MAJOR issue that I think I saw multiple times in other posts that affects most of the system.
Windows 10 has a completely broken proxy auto detection.
It is invisible and does not affect internet browsing but about of a half of a system processes is then plain broken due to that bug. Those processes cannot communicate.
It means but not limited to - XBOX application will not log you in, in the settings 'accounts' section you cannot login into Microsoft account claiming 'you are not connected to Internet', Windows Store is not working, Office 365 cannot connect to servers and neither create account nor get mail (while internal Mail client in Win10 works fine with same Office365 account), etc.
Naturally, your network status is shown happily connected to that Internet, no troubleshooters detect anything, there are no visible signs of any issues, it is all hidden into Win10 guts.
I was hit by it initially when I installed Office 365 and Outlook 2013 was unable to connect to our corporate exchange server, for no obvious reason.
At the same time, Windows update would not be able to work popping up incomprehensible error 0x80240438.
A first partial solution is to proceed to
Control Panel\All Control Panel Items\Network and Sharing Center
then click at 'internet option' in the lower left corner, go to 'connections' tab and into 'lan settings' and uncheck this dreaded checkmark in the 'autodetect' proxy feature. that will make most applications happy. It gets set 'checked' by default.
BUT NOT THE CORE WINDOWS BITS SERVICE!!! Developers worked long and hard to make this system unfixable.
All default jobs for downloads are submitted into BITS with proxy set to 'AUTODETECT'. That efficiently results in your windows store application unable to download anything, in you windows update unable to download anything - it does not error out, of course, it just starts download and sits stuck in there forever at 0%. To see what is going on you need to use bitsadmin tool from the command prompt ran under admin privileges and look at the list of tasks -
bitsadmin /list/ allusers
or read this
http://answers.microsoft.com/en-us/...e/17f48b91-c12c-41de-8c3a-63954cd40639?auth=1
and this
http://blogs.technet.com/b/networki...-to-test-the-bits-client-on-your-machine.aspx
In the test above you can see if you submit a job with NO_PROXY specified - it works like a charm.
but if you do that
Bitsadmin /setproxysettings bitstest preconfig
or that
Bitsadmin /setproxysettings bitstest autodetect
- you get same exact situation with a bits job hanging forever.
If you run
bitsadmin.exe /Util /GetIEProxy LocalSystem
and then
bitsadmin.exe /info {--job_id--} /verbose
you will see that windows keeps posting all jobs into BITS enforcing AUTODETECT as a default ignoring your settings.
you can use
bitsadmin.exe /Util /SetIEProxy LocalSystem NO_PROXY
- it does set it correctly, but, you have guessed right - Windows 10 does not give a damn what it is you set up and keeps creating jobs with AUTODETECT that never works.
WORKAROUNDS
as ridiculous as Microsoft is, workaround is also of a same kind. If you have a work VPN - Cisco or anything - there is a 90% chance that if you connect to VPN over same network adapter - it will work fine - that is my solution.
Other solution is to create an actual d@mn proxy in your proxy-less network and configure it manually into BITS using same bitsadmin, and with some luck it may start to work.
On my machine it sometimes starts to work and download updates after I reset winsock and tcp4 but it 'fixes' itself overnight and next day it does not work again.
NOTHING of what I explained above is within understanding of this Indian support that may call you if you open a ticket, they act like they hear words BITSADMIN for a first time in their call center lives, that may be indeed a true fact.
Still, it is very annoying and very frustrating. And took me some time to dig to the root of it.
I am still unable to find why original proxy autodetect is broken - all Intel drivers were tested, router udated, DHCP removed from router and moved into Linux DHCPD process and back, fixed IP address was set on the interface, IPV6 added and removed from both Windows and router - nothing so far did any difference to make autodetect work.
Where it works is our corporate network where there is a hardware proxy solution and DHCP serviced from a corporate switch.
Last edited: