WIN­DOWS UP­DATE BREAKS YOUR PC!

In­stall Mi­crosoft’s emer­gency fix

Computer Active (UK) - - Front Page -

Mi­crosoft has re­leased an emer­gency fix for a Win­dows 10 up­date that stopped USB ports, lap­top cam­eras, key­boards and mice work­ing prop­erly.

The prob­lems oc­curred be­cause the KB4074588 up­date, re­leased on 13 Fe­bru­ary, didn’t in­stall nec­es­sary new driv­ers for de­vices, and unin­stalled some that were still re­quired. It only af­fected com­put­ers that have up­dated to the Fall Cre­ators Up­date (FCU, version 1709).

Frus­trated users re­ported other prob­lems, in­clud­ing no text in the right-click menu, no text un­der desk­top icons, a tiny ‘cmd’ win­dow and sev­eral changed set­tings. Some even said their com­put­ers were crash­ing, pro­duc­ing the no­to­ri­ous ‘INACCESSIBLE_ BOOT_DEVICE’ Blue Screen of Death.

Prob­lems with the fix

Mi­crosoft re­leased a fix – KB4090913 – three weeks later. It was an un­sched­uled up­date, is­sued a week be­fore its reg­u­lar ‘Patch Tues­day’ se­cu­rity up­date. How­ever, the com­pany ad­mit­ted on­line ( www.snipca.com/27239) that the new up­date has prob­lems that stop it in­stalling. One is caused by “in­com­pat­i­ble” an­tivirus soft­ware. Mi­crosoft told users to con­tact their an­tivirus provider to check it’s been up­dated for the FCU.

In some in­stances, the er­ror mes­sage 0x80070643 ap­pears, and Win­dows re­verts to the pre­vi­ous version (the Cre­ators Up­date, 1703). Mi­crosoft said it will re­lease an­other up­date to fix this. Un­til then, you could try run­ning its ‘.NET Frame­work Re­pair Tool’ – fol­low the in­struc­tions at www.snipca.com/27243.

Cor­rupt Up­date files

Users also com­plained about other er­ror mes­sages dur­ing a failed in­stal­la­tion, in­clud­ing 0x80240031 and 0X800F081F. Mi­crosoft sug­gests the for­mer is caused by cor­rupt Win­dows Up­date files and can be fixed with its Trou­bleshooter tool ( www.snipca.com/27245); the lat­ter re­quires cre­at­ing an ISO file of Win­dows 10 us­ing the Me­dia Cre­ation tool ( www. snipca.com/27244).

The up­date should have been in­stalled au­to­mat­i­cally on your com­puter – check by click­ing Set­tings, ‘Up­date & Se­cu­rity’, Win­dows Up­date.

If not, try a man­ual up­date from www.snipca.com/27240 – click the cor­rect Down­load but­ton for your sys­tem. For ex­am­ple, if your com­puter is

32bit, click the x86 Down­load but­ton (and x64 if it’s 64bit). If your PC is pow­ered by an ARM pro­ces­sor, not In­tel, click the bot­tom Down­load but­ton (see screenshot).

De­spite the prob­lems with the FCU, Mi­crosoft still plans to re­lease the next version of Win­dows – Spring Cre­ators Up­date (1803) – in April. It says it will sup­port this un­til De­cem­ber 2019, which is the typical 18-month life­time of­fered by Mi­crosoft. By then, an­other three ‘fea­ture’ up­dates would have ar­rived, as­sum­ing Mi­crosoft sticks to its twiceyearly re­lease sched­ule.

Newspapers in English

Newspapers from UK

© PressReader. All rights reserved.