Bork Tuesday, Any Problems Yet?

It did install for me as well after a reboot and I don't have a recovery partition. https://www.wilderssecurity.com/threads/bork-tuesday-any-problems-yet.370217/page-318#post-3179591

https://www.wilderssecurity.com/threads/bork-tuesday-any-problems-yet.370217/page-318#post-3179573

 

This implies to me MS has modified the update to basically run a bogus update that no longer updates the RE partition to clear the previous failed update status.

 

It failed Twice but in the end it says successful.

 

Hi Dan,

Something funny is going on with my laptop, and I will find out, after a restart.

 

Latest from MS on the failed KB5034441 update. Update script available: https://www.bleepingcomputer.com/ne...update-windows-10-winre-with-bitlocker-fixes/ . Looks to me worse than doing the fix manually.

 

I just checked for updates and they are releasing a Preview already.

https://blogs.windows.com/windows-i...-build-19045-3992-to-release-preview-channel/

 

I have two laptops, one bad and one good. I am posting on the good one while the other one is updating, as I mentioned above.

Edit: I should say one is laptop, and the other is craptop!

 

My craptop is back from the dead, so to speak:



With the following chaser...



NB. Note the time... 8:16 AM

 

A funny thing it tried again today to install (KB5034441) one Failed and one Success without me knowing??

 

Seeing is believing! I have the latest build!!!!



BTW, I have blocked Windows Updates, for the time being, to my Windows 10 Pro laptop until this fiasco by Microsoft has died down.

 

I have the new Preview installed.

 

Good for you.

 

But, for me I don't like to be boned by Microsoft, so I have postponed for [Windows 10 Pro]...



...and I can keeping extending the resumption date for getting updates.

 

I tried again this evening to install the update on Win 10 with the same results, error.

 

I didn't get offered that update here.

Yes, same error here too.

What a cluster puck!

 

I am less brave and have postponed the MS updates on my Win 10 Pro machine until February 15, after the next Patch Tuesday.

 

I agree, these scripts don't look like a very good or realistic solution. For one, I'm somewhat comfortable with PowerShell but these scripts are as confusing to me as the original instructions from MS. Second, if I wanted to resize the recovery partition I'd do it manually. Third, why would I trust an automated script from MS after they already borked it so badly in the first place? I'm just going to keep ignoring this update till MS comes up with a better solution.

 

Reflecting back on my prior;

posting, I know what happened.

I had Win Explorer set to show "hidden files, folders, and drives." When the new recovery partition was created per MS fix instructions, Win Explorer created a drive letter for it; basically un-hiding the recovery partition.

Just running;

run cmd (admin)
mountvol F: /d

only would have fixed the issue in my case.

This does show how just one non-default Windows setting can bork the MS fix procedure.

 

Sounds like a good idea. I believe I'll do the same before M$ puts out more hosed updates trying to fix this last borked one.
I'm beginning to believe M$ does some crappy testing before releasing these updates to the public.

 

It's called the Windows Insider program...

 

insider and dev is much overrated.

 

No previews for me. They are just trying to sell more bloat, can't even get the updates right.

 

why not just reject it for now the update was pulled by MS earlier today

 

for those with 0x80070643 KB5034441.
check size of winre-partion, 500mb minimum
and check if enabled -> reagentc /info