hes deploying this already.... is strange IT dont like to move to a new OS right away or is a smart practice to do so, with out giving this some time to see if this is secure enough....in year or so will find out if hacker turn win10 into Swiss cheese
well a friends company have been testing insider builds so its pretty normal to find out whats best and try to shape the os
u told him to do it even though he would have to install rtm anyway to leave the insider preview? seems legit
That's not how it works. They don't have different builds for Insiders and public. The only difference is the labeling on the indexes which doesn't translate to what's installed on the system. If this is the Anniversary build that many seem to think it is, there will be absolutely no difference.
This could be RTM, I thought 14393 might have been only because it sounds good . I highly doubted it would be 14400 due to '4' being considered bad luck in certain cultures. The real question is, if this is 'RTM' build number, whether the actual release will be this plus an additional download update, or whether a future update will be incorporated into the ISO. Remember Microsoft have released newer ISO's with the cumulative packs after 10586. So basically, 14393 could be the RTM base build, but the final OS build could be with a '.x' (where x is a number). This would just be the 14393 files in addition to any files changed since. You have to consider that even though the build number of files changes in these builds, the majority of them probably haven't had any code changes (they won't be bit identical due to the version number difference etc). If 14393 is the final and there are updates before 02 August, we'll possibly have a test update, and even possibly multiple test updates. If this followed the recent build trend, and 14393 is 'RTM', then the first test build would be out in a few days, next one say, Wednesday next week with any final corrections, and then the final one pretty much on release day. This is pure speculation though. When Redstone 2 is in testing, if Microsoft achieve what has been rumoured, in that we will receive builds as updates and not full builds (so only the changed files) we may be seeing builds relatively frequently. Insiders probably remember previously how there was extended periods without new builds which was a bit annoying. At least if the builds come as updates having them frequently would be nice, having two builds a week for months would get a bit much after a while, but an update just containing the changes, and maybe a full build ever couple of months (so the cumulative updates don't get too big, and to test out the update system), that would be great! Back to this build, I do notice that the ISO created is a little smaller, by a little over 11 MB, than 14390. The size difference seems to relate to some non-interesting stuff though, looks more like they did a bit of a build cleanup.
because that would be stupid as even a RTM needs a final testing before launch and the fast ring the crazy bastards here are the ones for the job where you not here for the last two RTM of windows 10?
As long as there isn't a Microsoft announcement about the RTM, all that saying and posting are simply RUMOR!
It is true that this is not the "RTM" since M$ got rid of that term long time ago, why can't people just accept it? "The final build" will be more appropriate. Anyway, there are lots of evidence show it is "the final build": 1. Look at the url difference, before they are always something like: "announcing-windows-10-insider-preview-build-xxxxx-for-pc-and-mobile", now this one changed to "build14393" 2. At the end of the blog, Dona said: "All right, that’s all for now. Have an excellent week, team." 3. 10240 was pushed on July 9th, 20 days before the release; today is 18th, 15 days away from the release. If this is not "the final build" yet, they won't have time to release it to manufactures. 4. The registry key "SkipZDP" is no longer present in this build, which was exist in 14390.
Wait does that mean there will be no builds in this week. Kinda bummer. Most likely the next week's build might be the final build or RTM or whatever.
I don't use Windows 10 due to the bug (automatic installations of drivers and updates), so i don't remember correctly these nuances.
it_IT x64 pro File Name: 14393.0.160715-1616.rs1_release_CLIENTPRO_RET_x64fre_it-it.esd Url: tlu. dl .delivery.mp.microsoft.com/ filestreamingservice/files/a1bee904-c054-4d5e-ae48-0d42e37ce095?P1=1468948559&P2=301&P3=2&P4=gv6SInht2n%2bteKvERH3ue9If3dbcH%2bqpAPlSlemFX4w%3d Expire At: 19/07/2016 17:15:59 UTC SHA-1: 4C9F68D4E828B954D2D3BF08F05AE2B6DC64F690 SHA-256: 32204694B4F64392BCD6627293E6F72A6CA6FF14F7C0AA025938AE944CFB05E0