there's actually a method to disable it, create a nullroute in your hosts file: 127.0.0.1 vortex.data.microsoft.com 127.0.0.1 telecommand.telemetry.microsoft.com.nsatc.net Code: C:\Windows\System32\drivers\etc>ping telecommand.telemetry.microsoft.com.nsatc.net Pinging telecommand.telemetry.microsoft.com.nsatc.net [127.0.0.1] with 32 bytes of da Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Ping statistics for 127.0.0.1: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms C:\Windows\System32\drivers\etc>ping vortex.data.microsoft.com Pinging vortex.data.microsoft.com [127.0.0.1] with 32 bytes of data: Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 Ping statistics for 127.0.0.1: Packets: Sent = 3, Received = 3, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms Eventually check your events.log to find out which app doesn't connect repeatedly. That's how we could find the telemetry service maybe. I agree, more cloud is one the worst of all ideas. More privacy would be the better track. What's interesting about the vortex domain is the timing, it connects about every 5 minutes. Now I read Alan Henning, an aid official, has been beheaded by ISIL. Even the NSA couldn't help - that's the sad part about this "world order" tracking story!
maybe they turned it off for the weekend. When I ping either vortex.data.microsoft.com or telecommand.telemetry.microsoft.com.nsatc.net I get nothing.
Explorer is linked against two interesting new DLLs: NotificationController.dll and NotificationControllerPS.dll. They're both native code, one exports startup/shutdown methods for a COM server, so I guess they're COM/WinRT based. Maybe they've got something to do with the notification center.
I created a system image just to see if there was any difference in the procedure upon completion. There is no difference from Windows 8.1... no opportunity to create a repair disk is offered. I think that it would have been nice to put that repair disk option back in place since not everyone has a burned copy of the same OS to use to recover the image.
Here's a new one (to me). I know its a program or something requesting to open a port. But, only the Win10 machine is doing this. There are no other records in the router logs of this, except for the Win10 TP machine. Code: [UPnP set event: add_nat_rule] from source 192.168.1.4, Friday, October 03, 2014 20:27:52 [UPnP set event: del_nat_rule] from source 192.168.1.4, Friday, October 03, 2014 20:27:52 [UPnP set event: add_nat_rule] from source 192.168.1.4, Friday, October 03, 2014 20:27:12 [UPnP set event: del_nat_rule] from source 192.168.1.4, Friday, October 03, 2014 20:27:12 [UPnP set event: add_nat_rule] from source 192.168.1.4, Friday, October 03, 2014 20:26:27 [UPnP set event: del_nat_rule] from source 192.168.1.4, Friday, October 03, 2014 20:26:26 [UPnP set event: add_nat_rule] from source 192.168.1.4, Friday, October 03, 2014 20:25:42 [UPnP set event: del_nat_rule] from source 192.168.1.4, Friday, October 03, 2014 20:25:41 [UPnP set event: add_nat_rule] from source 192.168.1.4, Friday, October 03, 2014 20:25:08 [UPnP set event: del_nat_rule] from source 192.168.1.4, Friday, October 03, 2014 20:25:08 Apparently Win10TP is making use of UPnP constantly. -ed- Disable the UPnP in router ended that spamming. Dunno why I didn't have it off already anyway haha now back to normal logging lmao Code: [DoS Attack: SYN/ACK Scan] from source: 92.222.38.142, port 53, Friday, October 03, 2014 21:00:28 --- Paris, Ile-de-France, France. [admin login] from source 192.168.1.115, Friday, October 03, 2014 20:58:34 [DoS Attack: RST Scan] from source: 107.14.47.123, port 443, Friday, October 03, 2014 20:57:24 ---- Time Warner Cable Internet LLC California, Los Angeles CA [DoS Attack: RST Scan] from source: 209.18.46.162, port 443, Friday, October 03, 2014 20:57:24 ---- Time Warner Cable Internet LLC Kansas, Witchita [DoS Attack: RST Scan] from source: 107.14.47.122, port 443, Friday, October 03, 2014 20:57:21 ---- Time Warner Cable Internet LLC California, Los Angeles CA [DoS Attack: RST Scan] from source: 173.252.103.16, port 443, Friday, October 03, 2014 20:56:36 ---- Facebook, Inc. [DoS Attack: RST Scan] from source: 23.67.56.41, port 443, Friday, October 03, 2014 20:54:23 ---- Akamai Technologies, Inc. [DoS Attack: RST Scan] from source: 23.216.10.153, port 443, Friday, October 03, 2014 20:54:22 ---- Akamai Technologies, Inc. [DoS Attack: RST Scan] from source: 23.216.10.193, port 443, Friday, October 03, 2014 20:54:22 ---- Akamai Technologies, Inc. [DoS Attack: RST Scan] from source: 23.216.10.203, port 443, Friday, October 03, 2014 20:54:22 ---- Akamai Technologies, Inc. [DoS Attack: RST Scan] from source: 23.67.56.41, port 443, Friday, October 03, 2014 20:54:22 ---- Akamai Technologies, Inc. [DoS Attack: RST Scan] from source: 74.125.224.161, port 443, Friday, October 03, 2014 20:48:18 --- Google Inc. Nothing to worry about here, normal blah blah at router end.
hmm not necessarily... it could only be a one-way thing similar to utp. nexus did mention it did some sort of encryption handshaking or something. Perhaps it doesn't respond unless the magic words are spoken.
I think this is true for every partition larger than 32 GB. FAT32 can only be used for partitions up to that size in all Windows versions.
interesting, on commandline it's still shown: Code: C:\windows\system32>format /? Formats a disk for use with Windows. FORMAT volume [/FS:file-system] [/V:label] [/Q] [/L] [/A:size] [/C] [/I:state] [/X] [/P:passes] [/S:state] FORMAT volume [/V:label] [/Q] [/F:size] [/P:passes] FORMAT volume [/V:label] [/Q] [/T:tracks /N:sectors] [/P:passes] FORMAT volume [/V:label] [/Q] [/P:passes] FORMAT volume [/Q] volume Specifies the drive letter (followed by a colon), mount point, or volume name. /FS:filesystem Specifies the type of the file system (FAT, FAT32, exFAT, NTFS, UDF, ReFS). even exfat.sys is still there: Code: C:\Windows>dir exfat* /S /A Volume in drive C is Windows 10 Volume Serial Number is 2A5C-C945 Directory of C:\Windows\System32\drivers 13.09.2014 09:20 202 240 exfat.sys 1 File(s) 202 240 bytes but also refs.sys Code: C:\Windows>dir refs* /S /A Volume in drive C is Windows 10 Volume Serial Number is 2A5C-C945 Directory of C:\Windows\System32\drivers 13.09.2014 09:20 1 154 512 refs.sys 13.09.2014 09:20 924 624 refsv1.sys 2 File(s) 2 079 136 bytes well, exfat is still there, just formatted:
New keyboard shortcuts : (for task view) CTRL+WIN+D : create new desktop CTRL+WIN+F4 : delete desktop CTRL+WIN+ left or right arrow : move to other desktop
As W10TP is not able to install floppy disk and controller drivers, i tried to take the inf files from W8.1 + updates with no luck, they are refused, even i u try to install them manually from add device, floppy controller is empty,no models are included