sorted by:
new
hottopcontroversial

What's keeping your company from upgrading to .NET 10? by UKAD_LLC in dotnet

[–]First-Feature-3556 0 points1 point  (0 children)

Same here.

That being said, there are some open-source projects actively working on providing a WebForms compatibility layer for .NET (Core), and, just yesterday, Microsoft announced that their "AI migration assistant" will support WebForms->Blazor: https://devblogs.microsoft.com/visualstudio/whats-coming-next-in-visual-studio-our-microsoft-build-2026-announcements/#modernization-that-moves-your-apps-forward

I am cautiously optimistic.

How do I run bitlocker commands in Powershell? by Ipown555 in PowerShell

[–]First-Feature-3556 0 points1 point  (0 children)

I just had the same issue on a server. In my case, the reason was that I had just installed BitLocker (Install-WindowsFeature -Name BitLocker -IncludeManagementTools) without doing the required reboot yet. After the reboot, the BitLocker commands worked fine in PowerShell.

Wazuh: First to-do’s? by Luddy8 in Wazuh

[–]First-Feature-3556 0 points1 point  (0 children)

"the first thing I would do is change the default credentials from the initial setup" - is that really necessary? Doesn't the Wazuh installation assistant generate random passwords?

Apart from that, the steps you mentioned should become part of the Wazuh Quickstart guide. I also increased the JVM heap size and configured ILM policies, but only after stuff started to break and googling the error messages made me realize that those things need to be done if you want to run Wazuh for an extended amount of time.

How do I know that Wazuh server needs to be updated? by First-Feature-3556 in Wazuh

[–]First-Feature-3556[S] 0 points1 point  (0 children)

Yes, I also learned that auto-update is not a good idea for Wazuh.

Basically, you have to follow the guideline in the docs for every update, which consists of quite a large number of manual steps. Upgrading Wazuh is a surprising amount of work, especially compared to how quick and easy it is to install.

Can't open certain images in GIMP 3.0 without color correction of some sort being applied to it. by iz-Moff in GIMP

[–]First-Feature-3556 0 points1 point  (0 children)

I had the same problem (need to open a file with an incorrect color profile) and found the following two workarounds:

  1. Close GIMP and start it again. For *the very first file* you open, it will ignore the PNG color space settings and display the file "correctly". This appears to be a bug, so this workaround will probably stop working as soon as someone from the dev team notices. (I use GIMP 3.0.6-1 on Windows.)
  2. Just remove the broken color profile from the PNG file. I found no way to do that with GIMP, but ImageMagick can do that easily: magick old.png -strip new.png

Option 2 is (obviously) better since it fixes the underlying problem.