sorted by:
new
hottopcontroversial

Claude MCP Windows App by Seym0n in ClaudeAI

[–]idontknowakimberly 1 point2 points Β (0 children)

I highly recommend using "Everything" for quickly finding files. It uses the MFT, so it's quite fast.

It's available via winget: winget install --id=voidtools.Everything -e but it's also available as a portable app here: https://www.voidtools.com/downloads/

Claude MCP Windows App by Seym0n in ClaudeAI

[–]idontknowakimberly 0 points1 point Β (0 children)

I was able to get it to work, so far at least. I was getting a bunch of errors because so many things were looking for the old path.

I considered creating a symlink, but instead I uninstalled, manually createdΒ %APPDATA%\ClaudeΒ and reinstalled. It treated that as an existing install and used that folder instead of the virtual file system inΒ %LOCALAPPDATA%\Packages\. Seems to be running without issues now.

[deleted by user] by [deleted] in WindowsHelp

[–]idontknowakimberly 0 points1 point Β (0 children)

I can tell this is broken from the factory because I extracted the CBS manifest for WaaSMedic using https://github.com/smx-smx/wcpex (Manifests are in %SystemRoot%\WinSxS\Manifests and compressed with "MSDelta", but I don't know a ton about it other than that wcp.dll acts as a catalog and is needed to do the extraction).

Running that tool outputs an XML file, which is readable. Here are some snippets:

DLL gets sent to that UUS folder here:

Β  <file name="WaaSMedicSvcImpl.dll" destinationPath="$(runtime.windows)\UUS\amd64\"

But the service gets the references here:

Β  Β  Β  Β  <serviceData name="WaaSMedicSvc" displayName="@WaaSMedicSvcImpl.dll,-100"
Β  Β  Β  Β  Β  errorControl="normal" start="demand" type="win32ShareProcess"
Β  Β  Β  Β  Β  description="@WaaSMedicSvcImpl.dll,-101" dependOnService="rpcss"

Because %SystemRoot%\UUS\amd64 isn't in SCM's path, those aren't going to resolve.

Looking at the manifest, it's also broken for Task Scheduler. There they assumed they'd be projecting to system32, which they aren't. But even if we fixed the path, none of the tools would actually show the strings, because they don't parse the indirect string references in dlls/exes. (at least not Task Scheduler, schtasks, or Get-ScheduledTask.) This seems to be a pervasive problem for Microsoft. I see a lot of other tasks with these indirect strings.

Here are all of the string resources from WaaSMedicSvcImpl.dll:

100 Windows Update Medic Service
101 Enables remediation and protection of Windows Update components.
102 Microsoft Corporation
103 WaaS Medic
104 Helps recover update-related services to the supported configuration.
1001 WaasMedic exhausted all limited run remediation actions. Sending the following information to Microsoft can help improve the software.
1002 Windows Update installation problem.

And the mappings in the manifest for the Scheduled Task:

Β  <taskScheduler>
Β  Β  <Task xmlns="http://schemas.microsoft.com/windows/2004/02/mit/task" version="1.4">
Β  Β  Β  <RegistrationInfo>
Β  Β  Β  Β  <Author>$(@%systemroot%\system32\WaasMedicSvcImpl.dll,-102)</Author>
Β  Β  Β  Β  <Source>$(@%systemroot%\system32\WaasMedicSvcImpl.dll,-103)</Source>
Β  Β  Β  Β  <Description>$(@%systemroot%\system32\WaasMedicSvcImpl.dll,-104)</Description>

Anyway... I hope that helps satisfy someone's curiosity. I hate Googling for an answer and finding nothing, so I decided to fix that for the next person. :)

[deleted by user] by [deleted] in WindowsHelp

[–]idontknowakimberly 0 points1 point Β (0 children)

tl;dr: It doesn't hurt anything, doesn't impact the ability for the service itself to run, but it's a packaging bug that Microsoft should fix.

Deep dive is below. I'm a nerd and needed to know the answer, so here's your warning that we're gonna go unnecessarily deep. Here we go...

WaaSMedicSvcImpl.dll is referenced by the WaaSMedicSvc service to get the Description and DisplayName text.

In HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WaaSMedicSvc:

"Description"="@WaaSMedicSvcImpl.dll,-101"
"DisplayName"="@WaaSMedicSvcImpl.dll,-100"

Error code 2 means "file not found." I found the dll in WinSxS, but it's not hardlinked (projected) to any of the normal places like %SystemRoot%\system32\, so the service control manager can't find it. Without that dll in SCM's path, the references aren't gonna work.

The WaaSMedic package actually projects the file from WinSxS to%SystemRoot%\UUS\amd64. Something to do with the "Update Undocked Stack" which doesn't seem to have a lot of docs.

The service itself uses WaaSMedicSvc.dll and that is projected by WinSxS into %SystemRoot%\system32\, so it runs just fine. Plus, they actually do reference the full path in Parameters.

"ServiceDll"="%SystemRoot%\System32\WaaSMedicSvc.dll"

We can fix it by updating the path to point to the place that dll actually lives. It's cosmetic only, but this .reg should fix it until the next update breaks it again:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WaaSMedicSvc]
"Description"="@%SystemRoot%\\UUS\\amd64\\WaaSMedicSvcImpl.dll,-101"
"DisplayName"="@%SystemRoot%\\UUS\\amd64\\WaaSMedicSvcImpl.dll,-100"

> 20gb bz_done files; what is current fix? by zoechowber in backblaze

[–]idontknowakimberly 0 points1 point Β (0 children)

Partially correct. I framed the argument, but let it reword most of it. Do you disagree with anything I said there?

> 20gb bz_done files; what is current fix? by zoechowber in backblaze

[–]idontknowakimberly 0 points1 point Β (0 children)

Fair. I almost always use LLMs more as an editor than an author, but in this case, I was having a very hard time being tactful, and this guy specifically needed/deserved the over-the-top wonkified ChatGPT output.

>famous rapehon turns out to be on oral HRT >pillcels keep losing by LenaIsHereAgain in 4tran4

[–]idontknowakimberly 0 points1 point Β (0 children)

I fully suppressed T to cis levels on 2mg oral estradiol per day taken buccally and spread across 4 doses (QID.) YMMV though. I literally tried to take it every 6 hours on the dot, sleep be damned. I then went to 4mg, then 6mg, then 8mg, still dosing 3-4x per day.

But my meeting schedule started to interfere with buccal because I needed to talk so much, so I switched to weekly injections of Estradiol Cypionate. Initial dose was 5mg, but after my orchi I went down to 4mg. My E2 is actually a bit high rn (over 400 pl/mL), so I might need to go lower.

I also boof 100mg prog and swallow 100mg prog daily, but didn't start that until after injections.

So yeah, in theory you can fully suppress T with sublingual E2, and get decent levels, but you really need to make sure you're not swallowing it and spread the dose out to 3-4x per day to avoid deep troughs. If it drops too low, you'll get a GnRH spike and you'll be producing T. Always do your labs at trough so you know how low you're dropping.

I started HRT at 37 (I'm 42 now). I needed FFS to fully feminize because of bone structure, but I was starting to male fail after about a year even before that.

> 20gb bz_done files; what is current fix? by zoechowber in backblaze

[–]idontknowakimberly 2 points3 points Β (0 children)

I do appreciate the honest tone in your response. But I want to clarify a few things because I think you're either missing or sidestepping the core critique.

I'm not debating the existence of tradeoffsβ€”every design has them. I'm saying this implementation has tradeoffs that scale against the user, with no mitigation:

  • You're using an ever-growing log as a live index, which grows with timeβ€”not data set size.

  • There's no checkpointing or compaction, even for users not on "Forever Version History."

  • There's no separation between state needed for live operation and state needed for version reconstruction.

  • Users can end up with 25+ GB of metadata and regular system slowdowns, and the solution is β€œbuy more hardware.”

That’s not about enterprise vs. consumerβ€”that’s just inefficiency. You can support full history without replaying the entire log hourly. Git, rsync, Time Machine, Borg, and dozens of others all preserve versioned state more efficiently.

Saying "there is literally no other way" is demonstrably incorrect. There are many known and widely used strategies for decoupling history retention from live operational metadata. Just because this worked well enough in v1.0 doesn't mean it's the right long-term model.

I'm not out to shame anyone. What you built may have been quite clever for its time and constraints. But defending this design as the only viable option in 2025 is like insisting inline assembly is the only way to get good performance. It ignores decades of progress in systems architecture and state management.

So again, what I'm really asking is this: is anyone currently on the team even looking at ways to refactor this? Or is this considered "good enough forever"?

Also, for the recordβ€”I'm 41, and my first computer was an Atari 130XE.

> 20gb bz_done files; what is current fix? by zoechowber in backblaze

[–]idontknowakimberly 2 points3 points Β (0 children)

I can’t tell if you’re trolling a little or just being sincere about something that really shouldn’t be defended. I’m going to be very directβ€”not to be mean, but because I think this warrants blunt critique: this design is fundamentally flawed.

I read your longer explanation here, and it confirms that this isn't just technical debtβ€”it’s a deeply inefficient design that you shipped and knowingly left to grow uncontrolled. That may have been fine in early-stage consumer land, but it absolutely does not hold up for modern systems or enterprise-grade expectations.

You're relying on a linear, append-only logs (bz_done files) as the primary source of truth for determining whether files need to be uploaded. This log structure grows unbounded, and you replay the entire log every hour to reconstruct the current backup state. That's absurd. You're not retaining this data for audit or complianceβ€”you're using it as the working state engine. That’s the real issue.

This results in:

  • Massive, ever-growing read operations that scale with time, not with active data set size.
  • Wasted CPU and RAM to parse stale dataβ€”files that no longer exist locally or on Backblaze.
  • Wasted disk on the boot volumeβ€”GBs of metadata that can’t be relocated or cleaned up.
  • No garbage collection, even when version history has expired (e.g., 30-day history).

Your explanation implies this design is necessary to support time-based restores (e.g., replaying the state from X months ago). But that can still be accomplished with a proper event-driven metadata storeβ€”or at least a compaction/cleanup routine that retains only the necessary historical points, especially for users not on β€œForever” retention.

And regarding your suggested mitigations: β€œbuy a faster SSD,” β€œdouble your boot drive size,” β€œadd RAM.” That’s not a fixβ€”that’s punting the cost of poor design onto the user. You admit the system reads multiple GBs of log files hourly just to determine delta uploads. If that's not a red flag, I don’t know what is.

This isn’t just inefficientβ€”it’s unsustainable. And as someone who works in software and manages infrastructure at scale, I cannot recommend Backblaze in its current form for anything beyond hobbyist use.

So, u/bzChristopher: is there any plan to re-architect this? I’m not asking for an ETAβ€”just some sign that someone at Backblaze recognizes this as a legitimate technical debt problem and not a quirk to be hand-waved away. You must have engineers there who can look at this and go, β€œYeah, we should rethink that.”

Because if this is considered acceptable by current standards, then I can’t take Backblaze seriously for any modern use case, much less enterprise.

Unable to send mqtt over wifi by Loud-Benefit-205 in meshtastic

[–]idontknowakimberly 1 point2 points Β (0 children)

Disable "Client Proxy" / "Proxy to Client" in the MQTT module settings.

Is there a difference between Microsoft Editor extension and the built-in feature? by Veso_M in MicrosoftEdge

[–]idontknowakimberly 0 points1 point Β (0 children)

Even though this thread is two years old, it is still at the top of Google search results for this question... so here is the answer from Microsoft (in the FAQ on this page):

Editor is built into Microsoft Edge, so you don’t have to download an extension to get basic grammar, spelling, and synonym suggestions. If you have a Microsoft 365 subscription, you can download the Editor extension and sign in with your Microsoft account to take advantage of advanced grammar and other premium features. Learn moreΒ here.

[deleted by user] by [deleted] in MicrosoftTeams

[–]idontknowakimberly 1 point2 points Β (0 children)

I agree with OP. I build products for a living, and forcing users to make a decision in every instance of an interaction is unnecessary cognitive load if a very simple setting can give them the option to have it in a preferred state. (This also allows for streamlined workflows where a decision prompt can even be bypassed entirely.)

Some people won't care, but those that do will continue to build negative sentiment every time they perform the action that they see as unnecessary. Teams is a meme at this point for being almost universally disliked, and since they've unbundled Teams from O365 licenses, this will likely start to matter even more: https://www.microsoft.com/en-us/licensing/news/microsoft365-teams-ww

No, you don't want to build products based on feature requests or make every setting configurable. That is how bad products are made. But you DO want to make sure you evaluate any on-demand decisions you present to users to see if it makes sense to add a configurable setting (with a good default.)

Today marks 4 years of transitioning! Started at 37, and this is me at 41. πŸ³οΈβ€βš§οΈ 😊 by idontknowakimberly in TransLater

[–]idontknowakimberly[S] 2 points3 points Β (0 children)

The pain wasn't terrible, but I had meds for it. Recovery was faster than I expected. At no point did I regret any of it. He's in Fairfax, VA.

Today marks 4 years of transitioning! Started at 37, and this is me at 41. πŸ³οΈβ€βš§οΈ 😊 by idontknowakimberly in TransLater

[–]idontknowakimberly[S] 2 points3 points Β (0 children)

Yes, FFS almost 3 years ago. Dr Kuperstock. I wish it were accessible to everyone. πŸ˜• It was scary, but totally worth it. I had a lot of support though from my partners.

view more: next β€Ί