I guess when there are updates for 8.1 or when its final...why waste ones time now if its not yet final
It it absolutely useless to talk about a repo for the Preview version. When the final is gonna be released we will take further steps to bring the repo online. And we have to take the preperation time into our consideration. Some talks among some people here are neccessary, too, to keep the repo up-to-date, then.
Same goes for me and the installer/uninstaller. Not sure what Microsoft are going to do in terms of Windows 8 support once Windows 8.1 is released, but there should be no need to use Windows 8 once Windows 8.1 is released since it's a free update. That said, there seems to be some incompatibilities with antivirus and other software currently, so I guess that would be a valid reason at least in the short term! I cannot add proper Windows 8.1 support to the installer since I do not know what the final name structure will be. Remember for Windows 8 Microsoft decided to go with Windows8-RT-kb.... which doesn't make any conventional sense, seeing as there is a Windows architecture called RT, and yet 8-RT is meant to stand for 'Windows 8 RTM'. That naming also suggests that when Windows 8 was released, their intention was to call Windows 8.1 something different, maybe 'Windows 8 R2' or something else.
microsoft will support the orginal windows 8 for sometime atleast 10 years with secuirty updates windows 8.1 comes with ie11 microsoft has stated in the past that it would never include and upgrade aka ie11 in any future service packs because of enterprise support this pretty much means that the orginal windows 8 will receive security updates for the full 10 years mircosoft would set its self up for a big lawsuit if it tried anything else also as for windows 8.1 it was i belive orginaly going to be windows 9 but due to so much anger over the start menu it was changed
I'm not sure what the point of your post is but, as Burf mentioned, once Win8.1 is out (RTM ver), there shouldn't be any reason not to use it. Burf, it's interesting that a few of the older updates in the repo (2779444, 2703761, 2693643) are named Windows6.2-KB.. But then MS must've thought that was confusing and started with the even more confusing Windows8-RT-KB.. naming scheme. Maybe they'll switch back to something like Windows6.3-KB.. since that more accurately describes the contents of the 8.1 updates. But it's hard to predict what MS will do anymore!
From the notes of the upcoming patch Tuesday: Update for Windows 8, Windows RT, and Windows Server 2012 (KB2822241) packages have changed binaries have changed this update needs to be reinstalled I'm guessing they'll whack a -v2 on the end of it, but it's Microsoft, so who knows! Also there is an updated camera codec pack.
Probably, but most likely only security updates. Non-security updates are likely to be very few for the preview, unless they fix something deemed critical. The preview is more so people can find any compatibilities with software and drivers, including software developers, it isn't intended for mainstream use. Also, there could be changes from the preview to the release like there was with Windows 8. The most notable of these was a change in the UI. The Windows 8 preview UI was an updated Windows 7 UI styling, then they went to the more basic current styling and got rid of Aero glass (which was overused for some things, but I still believe it should be there but used more appropriately).
Regarding .NET 4.5.1 Preview (KB2828152-v2) i did a VM fresh install test, installed KB2828152-v2, ran (ngen.exe executeQueuedItems) and the error (A new guard page for the stack cannot be created.) didn't occur, operation completed successfully. Obviously i first thought it may has something to do with .NET 4.5 updates, so i uninstalled them all on my main system, then installed KB2828152-v2, ran (ngen.exe executeQueuedItems), and again the operation completed without an error. i even installed the LDR branch, no error either.
Repo Updated Note: The "new" KB2822241 had the same file hash as the one already in the repo (it was not re-added). Added: KB890830-V5.2 (Additional/KB890830.Microsoft.Windows.Malicious.Software.Removal.Tool) KB2803821 KB2830615 KB2832418 (Additional/NET35) KB2833958 KB2833959 (Additional/NET35) KB2835361 KB2835364 KB2840632 KB2840633 (Additional/NET35) KB2842230 KB2843376 KB2844289 (Additional/NET35) KB2845187 KB2846071 KB2846618 KB2848322-v2 KB2850851 KB2852222-v2 KB2853466 KB2853556 KB2853772 KB2855269 KB2855336 KB2856657-v2 KB2857645 KB2858668 KB2859160 KB2859541 (Additional/Camera Codec Pack) Removed: KB890830-V5.1 (Additional/KB890830.Microsoft.Windows.Malicious.Software.Removal.Tool) (superseded by KB890830-V5.2) KB2784154 (Additional/NET35) (superseded by KB2832418) KB2790831 (superseded by KB2858668) KB2803756 (Additional/NET35) (superseded by KB2833959 & KB2804584) KB2823958 (superseded by KB2855336) KB2836380-v2 (superseded by KB2855336) KB2838669-x64 (superseded by KB2848344) KB2838727 (superseded by KB2846071) KB2839229-x86 (superseded by KB2855336) KB2841194 (superseded KB2855336) KB2844296-v3-x64 (Additional/Hyper-V) (superseded by KB2855336) KB2845690 (superseded by KB2855336) KB2846833-x64 (superseded by KB2855336) KB2847928 (superseded by KB2857645) KB2851998 (superseded by KB2855336) For updates required by Windows Update (WU_Satisfy folder): Added: KB890830-V5.2, KB2832418, KB2833959, KB2835361, KB2840632, KB2846071, KB2855336, KB2857645, KB2859541 Removed: KB890830-V5.1, KB2838727, KB2847928