MICROSOFT HAS PUSHED OUT an upgrade to the Windows 10 Anniversary Update which fixes a fault that caused PowerShell borkage, and another that caused machines to freeze at the account log-in screen on boot.
The so-called 'log-in freeze' glitch, which has been around since launch, has received an official fix in the form of update KB3176938. Microsoft's blog on the matter said that the company received "a small number of reports", which appears to be something of an understatement.
The bug seemed to be caused by a machine having multiple logical drives, or partitions, with app data, according to Microsoft, having been manually moved to another drive. This confused the Windows 10 log-in process and resulted in a hang.
The patch has now arrived, but it is difficult for those whose machine crashes on boot to log-in and apply it.
Apart from logging in with a second administrator account - which seems to work - Microsoft's official advice for installing the patch on an afflicted machine is to use the Recovery Console by holding Shift when selecting Restart at the log-in screen, and then selecting 'Go back to the previous build' (thus rolling back and having to patch all over again with the new update). Another way is to log-in in via Safe Mode.
Meanwhile, the PowerShell problem, which appeared with Build 14393.82 on 23 August, was fixed with the release of Build 14393.105 on 31 August, just as Microsoft promised last week.
PowerShell was crashing because a missing .MOF (Management Object Format) file was breaking PowerShell Desired State Configuration which IT administrators use to manage Windows 10's enterprise environment.
This build contains no new Windows 10 features, but was necessary to start fixing a number of bugs that have plagued the Anniversary Update since its release. µ
The US was using the spyware to snoop on terrorist groups like ISIS
Likely will be most-affordable of Apple's 2018 iPhone, claims report
Move will see firms whacked with a three per cent turnover tax
Oh, you've got a new phone next week Huawei? We had no idea