Microsoft traditionally release updates on Tuesday ... just enable the service to start on Wednesday via the job scheduler ... command line is: net start "Windows Update" and net stop "Windows Update"  (just make sure it's set to Manual).

 

As far as Driver updates, I agree with you 100% and more importantly driver updates are supposed to go thru some level of certification by Microsoft before being made available ... however, as we know from history Microsoft has been pretty poor at ensuring stability in drivers, hence our desire to NOT have them automatically installed.  

 

If the above doesn't meet your needs, then this is the alternative that Microsoft provide: https://support.microsoft.com/en-us/kb/3073930 .  BTW, not disagreeing with you at all ... it's frankly bizarre that end users have to go thru hoops, but given Microsoft's past with Win8.x where once again end users had to rely on other software to solve real issues with basic functionality of Windows 8.x OS, I'm not entirely surprised that has carried thru to Windows 10.

 

Cheers, Rob.

Disabling the service and enabling it on Patch Tuesdays doesn't really solve the problem. WU will simply download drivers and other unnecessary junk during that time.

 

And yes, I've seen that link. Funny how MS changed the wording so that it also says it's compatible with Windows 10, not just the Insider Preview. They know they stepped on the ball regarding updates, yet they don't want to admit it.

 

 

Microsoft traditionally release updates on Tuesday ... just enable the service to start on Wednesday via the job scheduler ... command line is: net start "Windows Update" and net stop "Windows Update"  (just make sure it's set to Manual).

 

Patch Tuesday is a thing of the past Rob.  Also - if you want out of the Insider program then you will need to rollback to your original OS.  

 

Regards

jja

 

 

Patch Tuesday is a thing of the past Rob

 

Well technically not until tomorrow

 

I wanted RTM not "Insider Preview" and expected to get RTM at the end of last month (June) ... that didn't happen, apparently Microsoft changed my EULA agreement regarding my MSDN Ultimate Subscription without any notification.  There clearly was NO indication that Windows 10 RTM would be excluded from my $4000+/yr subscription ... however, RTM went out folks like Dell, HP, etc. at the end of June so they can image the OS to their PC units.  So there's a big question mark around what exactly is RTM and will the software I produce work with RTM vs. Insider Preview.

 

It looks like some last minute changes did happen and the two versions are different ... this could be one reason why Microsoft is forcing updates as it would ensure whatever build went out to HP, Dell, etc. would get immediately updated on initial first time boot.  But that's great for Dell, HP, etc. but leaves us developers out in the cold wondering if our products will work.  Which is one key reason why I have the MSDN Ultimate subscription ... I need to know if my software will continue to work or not giving me some lead time to adjust if it doesn't.

 

Either way, I have no idea what will happen, not a great feeling for a developer.  Microsoft continues to baffle me.

 

Cheers, Rob.

Yea  - you gotta watch out for those marketing boys.  Not sure why my MSDN is only giving me 1 key for VS 2015 as 2013 had 5 I think.  And yes Ultimate has gone the way of the Dodo  No worries as most of the cool stuff like CodeLens is now in pro.

 

Just file all of your complaints to the 'Under New Management' department.

 

Cheers

jja

Yea - you gotta watch out for those marketing boys. Not sure why my MSDN is only giving me 1 key for VS 2015 as 2013 had 5 I think. And yes Ultimate has gone the way of the Dodo No worries as most of the cool stuff like CodeLens is now in pro.

 

Just file all of your complaints to the 'Under New Management' department.

 

Cheers

jja

Not sure if related to MSDN licenses, but Office 2013 had something similar. If you didn't want to pay a subscription to use Office, you could buy Office 2013 the same way as previously, with one caveat: You only get 1 license for 1 computer, for $149 (price of "standard" Office)

 

In the past with Office 2010 or 2007, the $149 "standard" edition would give you 3 licenses for use with 3 computers.

MSDN Subscription Pro and Ultimate, we get 5 keys for most products, but sometimes we only get one or two keys, depends on the product.  Entry fee for MSDN Ultimate is around $11,000-$13,000 (don't recall the exact number) with a yearly subscription after 1 year at $4000/yr or so ... it's supposed to get me everything Microsoft, but every year it seems to get me less and less.  

 

I'm downloading Windows 10 Enterprise x64 right now (finally showed up in my Subscriber downloads) and I only get one key.  It'll be interesting to see what the differences are from "Insider Preview".

 

 

Cheers, Rob.

MSDN Subscription Pro and Ultimate, we get 5 keys for most products, but sometimes we only get one or two keys, depends on the product.  Entry fee for MSDN Ultimate is around $11,000-$13,000 (don't recall the exact number) with a yearly subscription after 1 year at $4000/yr or so ... it's supposed to get me everything Microsoft, but every year it seems to get me less and less.  

 

I'm downloading Windows 10 Enterprise x64 right now (finally showed up in my Subscriber downloads) and I only get one key.  It'll be interesting to see what the differences are from "Insider Preview".

 

 

Cheers, Rob.

Are you putting that on a virtual machine?

 

Could you try downloading the released Pro and seeing if the telemetry is still forced?

Folks using Win10 should probably check this menu option. It appears that by default MS will be using customer's PCs to (re)distribute stuff!

 

Sort of their version of a torrent distribution scheme:

 

Thanks Billy

 

 

Folks using Win10 should probably check this menu option.

 

Hey Bill, have you tried the "upgrade" route on a box with Visual Studio 2012, 2013, 2015 (or any combo of)?  If so, any issues?

 

I haven't dared tried to do this on a development machine yet.

 

Cheers, Rob.

I burned a Win X MultiInstaller MSDN download and installed Win X Pro over my Insider build 10162.  It allowed me to opt out of of the Insider program which I did.  Things look normal.  Should be a great OS.

 

Cheers

jja 

My Windows 10 Home upgrade works OK with my Visual Studio Pro 2013. No big surprises.

 

Dick

My Windows 10 Home upgrade works OK with my Visual Studio Pro 2013. No big surprises.

 

Dick

VS 2015 now has most of the Ultimate stuff like Code-Lens.  Pretty sweet.  Need to get the Win 10 SDK now

 

Regards

jja

 

 

VS 2015 now has most of the Ultimate stuff like Code-Lens.

 

I haven't made time to try VS 2015 (installed ok) ... can't risk any production code sets in it yet.  The most productive tool I've ever added to the VS series has been JetBrains ReSharper.

 

Plan to move to Win10 once I can confirm any issues important to my needs are all sorted out (not related to Flight sims).  I'd like to get going with DX12 -- just never seem to have enough time.

 

Cheers, Rob.

The only issue we had was that it moved some folders around for Apache Cordoba.  Otherwise it is solid.  I build all our code with it because the Rosyln compiler is pretty sharp.

 

Going to run FSX in a virtual desktop tonight.  Win 10 is getting cooler by the minute.  680 SLI's rockin in an FSX cruise with ~250 FPS near Sonoma, CA.

 

Cheers

jja