120M : A VM DNS issue or Not?

[alanbjames]

When i reinstalled my PC last night windows updates took over 2 and a half ours to download the first 163.

My connection speed is fine, i get between 149 and 156 on speed tests and downloading elsewhere is fine. I did a Tracert and this is what it came out as...

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\alans>tracert update.microsoft.com

Tracing route to update.microsoft.com.nsatc.net [157.55.240.218]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 13 ms 11 ms 69 ms cpc8-cwma8-2-0-gw.7-3.cable.virginm.net [86.21.1
83.1]
3 8 ms 9 ms 12 ms swan-core-2a-ae7-2163.network.virginmedia.net [8
0.0.255.133]
4 12 ms 12 ms 11 ms brhm-bb-1b-ae3-0.network.virginmedia.net [62.253
.175.130]
5 13 ms 12 ms 10 ms brhm-bb-2b-ae3-0.network.virginmedia.net [62.254
.42.205]
6 * * * Request timed out.
7 18 ms 17 ms 17 ms tcl5-ic-2-ae0-0.network.virginmedia.net [212.250
.15.210]
8 17 ms 14 ms 16 ms m322-mp2.cvx3-a.ltn.dial.ntli.net [213.104.85.66
]
9 18 ms 22 ms 22 ms ae7-0.lon04-96cbe-1b.ntwk.msn.net [191.234.81.15
8]
10 87 ms * 86 ms ae13-0.nyc-96cbe-1a.ntwk.msn.net [207.46.44.160]

11 87 ms 85 ms 86 ms ae0-0.nyc-96cbe-1b.ntwk.msn.net [207.46.38.113]

12 91 ms 93 ms 94 ms ae11-0.ash-96cbe-1b.ntwk.msn.net [207.46.36.174]

13 98 ms 90 ms 91 ms ae21-0.was02-96cbe-1b.ntwk.msn.net [191.234.82.5
]
14 96 ms 93 ms 92 ms ae1-0.was02-96cbe-1a.ntwk.msn.net [204.152.141.2
06]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 127 ms 128 ms 122 ms ae23-0.dm2-96c-1a.ntwk.msn.net [191.234.81.151]

19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Users\alans>

[General Maximus]

It's not a dns issue, if it was the host name would not have resolved to an ip address and the trace route would have error'd out.

[qasdfdsaq]

Taking a long time to do nearly 200 updates is not unusual on any connection.