Is there any way to verify the integrity of the updates before installing? md5 etc.. also any official documentation supporting the future release of the additional 2 updates not mentioned on the WZOR leak?
Same here. Have now installed the Spring Update (after imaging my boot drive). I see a Store icon on the task bar (is that because it may possibly lead to ppl spending money)!? Apart from any security updates, all the updates to the Metro guff are completely irrelevant to me! Sorely disappointed not to see a "Remove All Metro Guff On Non Touch Devices" applet added in Control Panel. Now being offered a couple of updates via Win update. KB2928680 and KB2894853. Will install those in a sec after reading back a few pages.
It could just be because I /resetbase'd my system before updating. Or it could be related to sysprep/capping and installing that way before updating. There's a lot of reasons it could misbehave, but what's important, is that there's a solution if anyone else does this and experiences a problem. You can extract the 2919355 msu file to a directory such as c:\cabs\ Then you can reboot into any winpe windows image that allows dism commands (windows setup, windows recovery, etc) Then run these commands to Re-install over the KB2928680 files: Code: mkdir c:\scratch dism /image:c:\ /add-package /packagepath:c:\cabs\Windows8.1-KB2919355-x64.cab /scratchdir:c:\scratch rd /q /s c:\scratch The scratch directory is important in boot environments because without it, you only have 1gb to work with. As we all know, the fully extracted cab takes up much more room than that. Anyway, that's the fix if anyone else bones their system. EDIT: I'm starting to think my problem was more related to my disabling of Windows Defender and subsequent updating of the Windows Defender kbfile. No I'm not talking about the definition updates. There was an actual methodology update today...
I use this card too (drivepool of 8 HDs, Windows starts from a separate SSD). At boot the driver is not loading and the controller is flagged with a yellow exclamation mark (I/O error). I've to deactivate and activate the card, then the driver is starting fine. This happens with the MS driver and the newest from LSI (P18 -> v2.0.69.1) since the 17031 update. I'm somewhat clueless...
Don't sign-in with a Microsoft Account, and disable UAC. Most, if not all Modern UI apps are pretty much useless/unable to run now. Then just use the script to remove majority of them, uninstall the few that remaining via right-click, unpin the Store icon on taskbar (or untick the setting for it), and that's that.
There is no new KB2919442, the one that is officially on Windows Update is exactly the same as the leaked one!
You guys should try and go on the forum of the manufacturer and mention this. Perhaps they've already noticed it and released a beta driver or something...
What changes i need to be made in this script to include MS .NET Framework 3.5, Pro WMC, and pre-activated? I have the data.dat and tokens.dat files from Windows 8.1 Pro WMC activate. Thanks.
What's worse is that after a good few attempts the OS will actually boot every once in a while, but it's almost like playing Russian Roulette. I'm looking into it at the moment, about to enable boot logging then testing again, hopefully I should be able to grab the boot log and look through it and see where it's failing and what for. However, I do suspect that we may be looking at a new BIOS/Firmware from LSI as opposed to a fix from Microsoft because from what I can tell it's not driver related. I experienced a very similar issue to this last year with Server 2012 R2 on an HP MicroServer with an integrated Broadcom NIC and the solution was an updated BIOS from HP. What Firmware/BIOS do you have installed? I'm running the latest P18 IR Firmware/BIOS
Dear All, I found the reason for the above problem. Today I downloaded the Windows 8.1 AIO Spring 2014 x86 en-US DaRT 8.1 ESD from tpb by murphy78 and did a clean install. System was good till install and update Kaspersky Internet Security 2014. After the install and update (KIS2014) the systems failed to boot and got the same above issue of "restarting twice and option to repair. Did anyone here who uses KIS2014 faced the same? Regards, Manu
This was my first thought. But it seems that LSI don't have an open support forum. Maybe they are way to professional, aka don't like public complains about their products BIOS/Firmware/Drivers, all up to the latest. It's a reflashed IBM1015 to SAS 9211-8i IT-Mode. I think (maybe hope) that this affects Server 2012 R2 too. There are more people with such hardware and we will come to a solution when this update is officially released.
No sir, I am saying that the version does not appear on the start page as I have seen in other images. I know the update took as the version number in the registry is correct. Can you tell me how to make it appear on the start page? Thank you