Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft suggests command line fiddling to get Windows 10 update installed

theregister.com

Post reply on HN
Print view View original

101–110 of 223 posts

Re: Microsoft suggests command line fiddling to get Windows 10 update installed

#101

Post by johngossman »

EspadaV9 wrote: post #7

When installing the update, some users are finding themselves faced with an 0x80070643 error, a generic failure message. Unfortunately, according to Microsoft, "because of an error in the error code handling routine," this might not be the correct error. Error in the error code code is giving the wrong error code for the error. I'm curious how often the error code code needs touching that there is an error in there t…

Dating myself, but I used an OS/2 build that would occasionally report “This Error Message has been deleted”

Re: Microsoft suggests command line fiddling to get Windows 10 update installed

#102

Post by ryzvonusef »

I also got this error... if I understand this correctly, they want a recovery partition of 250 MB... but I already have a recovery partition of 500 MB (acc to disk management, and lists it as 100% free)... so why am i getting this error?

should I increase it by a further 250 MB (for a total of 750 MB), or are they just plain crazy?

Re: Microsoft suggests command line fiddling to get Windows 10 update installed

#103

Post by krger »

sixothree wrote: post #99
bheadmaster wrote: post #10

Glad to see that Microsoft is making Windows more and more similar to Linux by every passing day :)

Did a fresh install of windows 11 yesterday and winget doesn’t work. Seriously. I haven’t even installed any software yet.

The output turns blue and nothing happens? Update Terminal and then winget will work.

Re: Microsoft suggests command line fiddling to get Windows 10 update installed

#104

Post by bhdlr »

Zyst wrote: post #55
msla wrote: post #30

Earlier quoted context omitted.

Yeah, this isn't Linux. Linux is better than this these days.

I use Linux. You absolutely need to drop down to the command line at times. Upgrading my Kennel, or Graphics driver breaks something like 20% of the time for me.

I think the point is that the Linux command line is more functional and easier to navigate than the Windows command prompt

Re: Microsoft suggests command line fiddling to get Windows 10 update installed

#105

Post by kotaKat »

sixothree wrote: post #99
bheadmaster wrote: post #10

Glad to see that Microsoft is making Windows more and more similar to Linux by every passing day :)

Did a fresh install of windows 11 yesterday and winget doesn’t work. Seriously. I haven’t even installed any software yet.

You have to wait for all the back-end updates to finish. Install all the Windows Updates, then open Microsoft Store and go to the Library and wait for it to update even more shit, then you finally will have Terminal and WinGet.

Yeah, I found that one out the annoying way too.

Re: Microsoft suggests command line fiddling to get Windows 10 update installed

#108

Post by jstummbillig »

hooby wrote: post #100
bheadmaster wrote: post #10

Glad to see that Microsoft is making Windows more and more similar to Linux by every passing day :)

I really do not agree with this comparison. Yes, it is true, that on Linux there are many, many things which are best done through command line fiddling. But installing a system update, that update borking things, belching up a totally cryptic error message, and then forcing you to clean up the mess through the command line, is nothing something I've experienced on Linux so far. For me, apt updates have always been s…

> For me, apt updates have always been super reliable - and error messages have mostly been quite specific and easy to google.

The ocean between. While you or me might appreciate a good error message and handy debugging options, the standard windows user experience is optimised to not confront users with errors at all. Either approach comes with its trade offs and is implemented with varying degrees of success.

Re: Microsoft suggests command line fiddling to get Windows 10 update installed

#109

Post by khaledh »

ryzvonusef wrote: post #102

I also got this error... if I understand this correctly, they want a recovery partition of 250 MB... but I already have a recovery partition of 500 MB (acc to disk management, and lists it as 100% free)... so why am i getting this error? should I increase it by a further 250 MB (for a total of 750 MB), or are they just plain crazy?

The update requires 250 MB of _free_ recovery partition space, not the total size of the partition.

Re: Microsoft suggests command line fiddling to get Windows 10 update installed

#110

Post by briHass »

londons_explore wrote: post #12

> a vulnerability that allowed attackers to bypass BitLocker encryption by using the Windows Recovery Environment (WinRE) I always wondered why the recovery environment seemed to let me have SYSTEM privileges to my auto-decrypted system drive... Thats been the case for years, and you can use it to dump the contents of a machine you've lost the login password to for example. I guess it wasn't supposed to!

Only if you don't use a TPM PIN and/or have a Bitlocker using TPM with PIN has no way to know your hard drive key without asking the TPM, which requires the PIN (and has anti-hammering/lockout built in.)
Post reply on HN