I know there has been a solution but the thread is in a mess, hope moderators could clean up a bit so we can get what we want. Instead of you saying all these, why dont you send me a link to the post ...
There are a few reasons the thread is confusing. At first, thread was created by someone who found a download link to the 10061 ESD in their system. This was before MS officially announced the release, so a major find. Soon, people were all over these, trying to make ISO for clean installs. There were problems, as the encryption key for the esd seems to have been different (the esd files were later re-releases from WU with the older encrypt key apparently). To avoid DMCA complaints and problems, the site administration is trying to minimize links to sources, even in directly on MS servers. The best approach so far (used in the 10056 thread) was to post links to Twitter posts, which could contain info and links to binaries. 85 pages is a lot to read thru, and a lot of people won't understand a lot of the posts, since things have been edited. The original post, for example, lost links to Twitter even, now it's only a generic 'what's new in this build'. I don't think that's the original author's fault, but the DMCA situation mostly. I read half of all those pages in sequence, and installed on my main test system (x86 version) as an upgrade via WU, that was flawless. There ARE some iso files around, made by third parties, but you do take a risk with those. I installed on a second laptop today, a clean install of 10061 ISO, and it has some strange bugs. You might be able to create your ISO, if you have the proper ESD, using the guide and tools used for previous releases. Cryptokey seem to have gone to the older key value, so the existing batch files should work, afaik. Maybe I missed something along the way.
the converted iso is available on the most popular torrent site(hint) if you want to get it there? though some might comment on if its a good place to get it?
Are you using Window 10 Pro Build 10061, if so try these cmds in Powershell. Code: cd "C:\Program Files\WindowsApps" Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "Microsoft.VCLibs.120.00_12.0.21005.1_x64__8wekyb3d8bbwe\AppXManifest.xml"} Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "Microsoft.VCLibs.120.00_12.0.21005.1_x86__8wekyb3d8bbwe\AppXManifest.xml"} Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "Microsoft.Cortana_1.4.3.156_x64__8wekyb3d8bbwe\AppXManifest.xml"} Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}
Did a clean install and this build is worse than the earlier. Start Menu opens only 2 times every boot and won't open anymore. Why would Microsoft release a build with a Start Menu that barely works? Sometimes system would just lock up during restart with no apparent reason. Just got to be a bad joke.
draken, I hear you. Worst part is that the Windows Update and Account Settings are now Metro-style apps. No Start Menu, no WU, no reset account or create a new one. I am at that point right now. Getting an ESD from kat, try to decrypt and create my own iso, reinstall. Else, going to older build on this machine (other one works ok, WU install was fine).
I moved my taskbar on TOP side instead of the default BOTTOM side. My Start Menu functioned well, so far.
this is intresting you say ...i try it but show me only one .exe nothing i use that Get-BitsTransfer -AllUsers | fl * >C:\address.txt same . what need change from this line ?
thanks anyway !!! in my lang there not exist but this info i learned more el-gr too hard find it and for now its not exist..