User Profile
SusanBradleyGeek
MVP
Joined Sep 12, 2016
User Widgets
Recent Discussions
Re: KB5034441 fails to install with error code 0x80070643.
Here's what doesn't make sense to me: 1. The risk of this vulnerability is in the enterprise space. Yet the patch isn't released to WSUS or on the Microsoft catalog site - those are the two landing spots for more enterprise patching. 2. One could argue that in this era of cloud first that WU is the the right target channel, but it's also offered up to EVERY Windows 10 HOME pc that probably doesn't have a TPM, doesn't have bitlocker anyway (they can only do drive encryption and down on that platform it's probably not enabled by default. So why not 3. have a more targeted deployment to ONLY those Windows 10 pro with bitlocker enabled. To release it to Windows 10 Home/Consumers that could possibly make their systems unbootable poking around their partitions is being more damaging to the consumer/home segment. There is little to no risk to a segment of patchers that problem aren't vulnerable to this security issue in the first place. As a FYI it was recommended to me to provide feedback to Microsoft in this venue. So I was trying as best as I could to be respectful. I am the long time patcher. So when I say "Feedback from a long time patcher": That's me I am talking about. I have been patching systems and computers and remember when Code Red hit the Internet and I couldn't figure out why ebay was so slow. Since before Microsoft update was a thing. Since before Patch Tuesday was on a Tuesday.16KViews0likes0CommentsRe: KB5034441 fails to install with error code 0x80070643.
I'm speaking on behalf of everyone dealing with this update and the frustration we all have. We're on month two with no good resolution other than potentially destroy your computer. I was trying to be diplomatic about my feedback. What I said here: "What you are asking your Microsoft patchers to do with this update is not acceptable and not attainable by your Windows 10 patching audience." still stands. This is feedback TO Microsoft.16KViews2likes0CommentsRe: KB5034441 fails to install with error code 0x80070643.
The January 2024 Windows RE update might fail to install Status Confirmed Affected platforms Client VersionsMessage IDOriginating KBResolved KB Windows 10, version 22H2 WI706429 KB5034441 - Windows 10, version 21H2 WI706430 KB5034441 - Devices attempting to install the January 2024 Windows Recovery Environment update (the Originating KBs listed above) might display an error related to the size of the Recovery Environment's partition. The Windows Recovery Environment (WinRE) is used to repair or recover from issues affecting Windows. Resulting from this error, the following message might be displayed. "0x80070643 - ERROR_INSTALL_FAILURE" Workaround: It might be necessary to increase the size of the WinRE partition in order to avoid this issue and complete the installation. Note that 250 megabytes of free space is required in the recovery partition. Guidance to change the WinRE partition size can be found in KB5028997: Instructions to manually resize your partition to install the WinRE update. Next steps: We are working on a resolution and will provide an update in an upcoming release.154KViews0likes7CommentsKB5034441 fails to install with error code 0x80070643.
Feedback from a long time patcher here: The manner in which this particular update has been handled has been poor in my opinion. The update is only being pushed out to Windows update or Windows update for business and is not on the Microsoft catalog nor WSUS. So this update has been pushed to machines that I would call "lightly" managed or "unmanaged". Some of these impacted machines have no TPM chip nor do they have bitlocker installed so the need for this update is nil. The communication thus far has been to instruct us to manually attempt to resize partitions which are not easy to do for anyone, and particularly not for a lot of machines. There are few tools that I can see that let us know if we're going to hit this issue other than to attempt to install and see if it fails. The PowerShell script is not something I'd have my 95 Dad want to do to his machine, let alone me wanting to do it to a bunch of machines at the office. We're now at Friday, right before patching weekend and may I request a lot more communication and perhaps someone going back and adding in detection into the patch to at least not attempt to install on machines that have no tpm chip and do not have bitlocker installed. These machines are not at risk. What you are asking your Microsoft patchers to do with this update is not acceptable and not attainable by your Windows 10 patching audience.184KViews10likes70CommentsRe: Recovering from a bad Quality Update, when its fix is released "Out of Band", using Intune?
Feedback hub is for insiders. Microsoft Support for business is what they recommend. https://support.serviceshub.microsoft.com/supportforbusiness/onboarding?origin=/supportforbusiness/create However I'd like to report that when I opened a bug for RDbroker service on Server 2022 getting removed with the March/April/May updates and we opened a support case, we were told by Microsoft support that they did not do root cause analysis unless we were a Premier customer. I had to use alternative means/social media to get someone to investigate the issue. Bottom line this process is not without issues as well.2KViews1like0CommentsServer 2022 loses RDconnection broker role upon install of March and April CU
Windows Server: Open issues from March 2022 Updates (KB5011551, KB5011497) | Born's Tech and Windows World (borncity.com) I have a support case open on behalf of a customer who after the install of KB5011497 has lost the RDconnection broker role on the server and it's broken. When we talked to support they told us "the team does no root cause analysis and that a case needs to be opened with the “premier team” in order for there to be any further analysis and an actual fix for the problem" Right now after installing the patch, breaking RDconnection broker one has to "removing the rdg, rdcb, and rdweb roles from the server (leaving RDSH intact) and reinstall them". This is unacceptable for patching behavior. It appears that the patch does not install the SSU and it's unclear if this is triggering the destructive behavior. 1. Is Microsoft aware of this issue 2. Are they planning to fix this?905Views0likes0CommentsServer 2022 lost RDgateway role during install of March Updates, what would cause that bug?
https://borncity.com/win/2022/03/09/windows-server-2022-mrz-2022-update-kb5011497-verursacht-probleme-mit-remote-verbindungen/ After the install of March updates on Server 2022, they lost the RDgateway role. What in the Server 2022 patches would specifically trigger this side effect? I did not see this on 2019 or 2016 servers so the bug is unique to 2022.1.6KViews0likes3CommentsRe: Introducing Buy now, pay later in Microsoft Edge
"may not have enough to even give presents". Then they shouldn't be signing up for debt. Christmas is not about presents and if you don't know that by now, you should. Group policy disablement hasn't been discussed and then that's only in Pro skus not consumers. I get it you think this is wonderful. May I ask which browser is default on your Windows machine?4.3KViews3likes1CommentRe: Introducing Buy now, pay later in Microsoft Edge
GraniteStateColin I'm a human being, network admin, security person, as well as someone who thinks this is just a bad thing to be building into a browser https://www.npr.org/2021/11/29/1059706124/examining-the-pros-and-cons-of-the-option-to-buy-now-but-pay-later "But generally speaking, if you don't have the cash now, you probably shouldn't be doing this." I like Edge. I honestly do. But then someone in management at Microsoft has clearly made a financial deal that just puts a bad taste in my mouth. My browser shouldn't be for sale like this to the highest bidder. Make it secure. Make it fast. Make super duper secure mode default. But stop doing boneheaded decisions like this.5.4KViews3likes0CommentsRe: Thick window title bar in office 365 applications
In the coming soon section in office (which I’ve found to be turned on) this enables this new look. Click on the megaphone on the upper right corner, scroll to the bottom of the page and disable the preview Coming Soon Coming Soon gives you an opportunity try new features and share feedback with us before the changes are released to all customers. Office has a fresh look. It’s modern and new, designed to help you focus on your best work. This new update includes: :black_medium_small_square:Simple, intuitive, and seamless experience across all your Office apps :black_medium_small_square:Customizable ribbon that you can change and create shortcuts to everyday commands you use the most :black_medium_small_square:Office themes that stay in sync with your Windows light or dark mode setting by default :black_medium_small_square:Share your work and collaborate with others in real time by selecting Share and sending your draft to whomever you want. Try the new experience On Turn on Try the new experience to try it and let us know what you think! We’re listening and are making more improvements based on your feedback.40KViews13likes8Comments
Recent Blog Articles
No content to show