New
#390
Windows 10 Anniversary Update Available August 2
I'm about one third finished with taking everything back to bare metal.
What I have done so far::
1. Unplugged all external hard drives.
2. Took everything back to bare metal: one huge 500GB unallocated SSD drive, then divided it into two partitions.
3. Installed Build 14393.5 ISO, but when finished, I only had Build 14393.0!!! What I think happened is that since the cumulative updates were short and sweet, they weren't included in "install.esd"; thus, didn't make it into the ISO. Makes sense to me.
4. And as some have said, without virtue of being on the Insider Program . . . yet, when I checked for updates I found I was updated to Build 14393.5!
That's my story and I'm sticking to it.
just playing around wynona. nothing that serious. lol.waiting till friday before i set the pc on fire. maybe.
Ran into the expiration on one of the early Insider VMs that didn't see any newer build go on when at first suspecting that was only 90days old when finding that many builds are scheduled to expire after a six month time frame. A few of the latest builds however that followed the 14385 are permanently activated!
The MC Tool will only download the general release of the last major update being the TH2 until RS1 is out. For any new downloads you should simply wait the few days in order to get the Anniversary update.
Not necessarily! I have the 385 still running on the main while the 393.5 is on the second and neither should the expiration date when running winver. The tool simply displays build number and edition type information. The correct method is to open a command prompt and type in "slmgr /xpr" which will then reveal either the expiration or if a particular build has the permanent activation status. The 14385 on the main here shows permanent while that will still be replaced by the RS1 update.
Night Hawk - your are batting -300 lately (is it possible to have a negative average?). Your build 14385 and 14393 did not show expiration dates in winver because Microsoft removed expiration from these builds. You are losing credibility with every post. Just like trying to tell us Microsoft would discontinue the MCT when the Windows 7 and Windows 8.1 Media Creation Tools are still available - and you were proved wrong on that one. In addition, slmgr /xpr tells you about your activation - not the expiration date of the OS installed. For example, people who upgraded to Windows 10 in July last year and then joined the insider program would have all those intermediate builds that had expiration dates, but their digital entitlements were permanent activations.
Not so! The winver tool does what it was designed for with the shortened name. Version of Windows providing edition and build information for version of Windows being run. The command prompt method is to display any and all expiration information.
The Wiki article that shows which builds will have expiration dates as well as those that are to be considered permanently activated can be at the MS Answers site. Complete list of Windows Insider build numbers and what happens when a - Microsoft Community
Why you don't find this at the WIP(Windows Insider Program) site is a mystery there but typical of MS.
Thank you for more incorrect information, I just realized, I have a Windows 10 installed with an expiration date because I installed Windows 10 home build 14372 for no other reason than to capture the install.esd file for build 14393 when it popped in Windows update. So.... here it is when you have a build installed that has an expiration date:
As you can see, the OS expiration is shown in winver and slmgr /dlv, NOT slmgr /xpr.
It getting really old having to correct your erroneous posts so people get factual information.
Last edited by NavyLCDR; 31 Jul 2016 at 22:26.