Yea, live tiles working for me now too (they did not before) I see no reason they would have any problems integrating into an offline image
Does anyone have the x86 versions of the rollup? Windows8.1-KB2883200-x86.msu Windows8.1-KB2894029-x86.msu Windows8.1-KB2894179-x86.msu ??
3. You understand that the official phone support is trained to provide support for the home user and do not cover professional Windows users (who often can find their solutions on dedicated paces like TechNet) and that the tier1 support do not cover the advanced user scenarios like manually installing a driver, right? But even though you can load a driver using INFs, all third-party stuff must be properly signed and of course compiled for the arm woa architecture used specifically by this platform. It is well known that ARM as being RISC arch has many variations, that differ, and drivers for one variation will not work on other. As the probability for an end-user to have such a third-party driver, which is not distributed by Microsoft through the Store and Windows Update frameworks, is very low, it is normal for any support service to answer the generic answer you heard. Note3. ah ok, thanks
Is there any particular reason why you placed KB2894179 ahead of KB2883200 in the install order? I'm curious because KB2894179 contains files related to the bootloader, not the servicing stack. And the files in KB2894179 are 6.3.9600.16415, which are newer than the 6.3.9600.16411 bootloader files in KB2883200.
It's probably to prevent 2883200 from installing certain files. WinSxS likes to keep 2 versions of files if you install an older version first. It likely does not matter if you use a /resetbase
Fantastic, thanks, Going to install it on my PC now! Hopefully some of the minor, but annoying, bugs will miraculously disappear. If you have access to the ARM/Surface RT GA Rollup that would be appreciated too.
Log: Initiating changes for package KB2894179. Current state is Absent. Target state is Installed. Client id: WindowsUpdateAgent. Windows update Update for Windows (KB2894179) requires a computer restart to complete the installation. Windows update "Update for Windows (KB2894179)" was successfully installed. Initiating changes for package KB2883200. Current state is Absent. Target state is Installed. Client id: WindowsUpdateAgent. A reboot is necessary before package KB2883200 can be changed to the Installed state. Windows update Update for Windows (KB2883200) requires a computer restart to complete the installation. Windows update "Update for Windows (KB2883200)" was successfully installed. Initiating changes for package KB2894029. Current state is Absent. Target state is Installed. Client id: WindowsUpdateAgent. A reboot is necessary before package KB2894029 can be changed to the Installed state. Windows update Update for Windows (KB2894029) requires a computer restart to complete the installation. Windows update "Update for Windows (KB2894029)" was successfully installed. A reboot is necessary before package KB2894179 can be changed to the Installed state. --- reboot --- Package KB2894179 was successfully changed to the Installed state. Package KB2883200 was successfully changed to the Installed state. Package KB2894029 was successfully changed to the Installed state. --- cleanup + resetbase : Initiating changes for package KB2880289. Current state is Installed. Target state is Absent. Client id: DISM Package Manager Provider. Initiating changes for package KB2883295. Current state is Installed. Target state is Absent. Client id: DISM Package Manager Provider. Initiating changes for package KB2883900. Current state is Installed. Target state is Absent. Client id: DISM Package Manager Provider. Initiating changes for package KB2884097. Current state is Installed. Target state is Absent. Client id: DISM Package Manager Provider. Initiating changes for package KB2884778. Current state is Installed. Target state is Absent. Client id: DISM Package Manager Provider. Initiating changes for package KB2885592. Current state is Installed. Target state is Absent. Client id: DISM Package Manager Provider. Initiating changes for package KB2889543. Current state is Installed. Target state is Absent. Client id: DISM Package Manager Provider. ------------- KB2883900, KB2884097, KB2884778, KB2885592 still offered by KUC after installation of this ODK rollup. Need updated database
Even with this update, Windows 8.1 is still crashing after a few sec. if you play two flash videos at the same time. Never had this issue on windows 7 or 8
Worked all ok.... Code: ---------------------------------------------------------------------------------------- | --------------- | ------------- | ---------------- Package Identity | State | Release Type | Install Time ----------------------------------------------------------------------------------------- | --------------- | ------------- | ---------------- Microsoft-Windows-CameraCodec-Package~31bf3856ad364e35~amd64~~6.3.9489.0 | Install Pending | Update | 12/10/2013 09:10 Microsoft-Windows-Client-LanguagePack-Package~31bf3856ad364e35~amd64~en-GB~6.3.9600.16384 | Installed | Language Pack | 22/08/2013 20:57 Microsoft-Windows-Foundation-Package~31bf3856ad364e35~amd64~~6.3.9600.16384 | Installed | Foundation | 22/08/2013 14:46 Package_for_KB2883200~31bf3856ad364e35~amd64~~6.3.1.18 | Install Pending | Update | 13/10/2013 10:57 Package_for_KB2883900~31bf3856ad364e35~amd64~~6.3.1.0 | Install Pending | Update | 12/10/2013 09:10 Package_for_KB2884101~31bf3856ad364e35~amd64~~6.3.1.9 | Install Pending | Update | 12/10/2013 09:11 Package_for_KB2886439~31bf3856ad364e35~amd64~~6.3.1.0 | Install Pending | Update | 12/10/2013 09:11 Package_for_KB2894029~31bf3856ad364e35~amd64~~6.3.1.0 | Install Pending | Update | 13/10/2013 10:57 Package_for_KB2894179~31bf3856ad364e35~amd64~~6.3.1.0 | Install Pending | Update | 13/10/2013 10:58 Package_for_KB976002~31bf3856ad364e35~amd64~~6.3.1.0 | Install Pending | Update | 12/10/2013 09:12 The operation completed successfully.