788
Microsoft is blocking Windows Customization Tools (www.neowin.net)
submitted 2 years ago by to c/technology@lemmy.world
261 comments fedilink hide all child comments
 

TLDR: StartAllBack, ExplorerPatcher and some other projects are being blocked on 24H2.

One more reason to switch to Linux

you are viewing a single comment's thread
view the rest of the comments
[–] 23 points 2 years ago* (last edited 2 years ago) (6 children)

Meanwhile the new settings panel is telling me my network is private while control panel and network share settings tell me it's domain authenticated.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 7 points 2 years ago (5 children)

    ...while you're sitting in an internet café

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 5 child comments
    •
  • [–] 8 points 2 years ago (4 children)

    It would be funny if true.
    Sadly the reality is me calling with a client because this one single PC refuses to apply the damn GPOs... :(

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 4 points 2 years ago (3 children)

    Every day I'm thankful for having found a job where in such a case I can just send out a pre-imaged replacement pc from the pile and have them send the old one back.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 3 child comments
    •
  • [–] 3 points 2 years ago (2 children)

    I would like to. Sadly there are programs on it that can be reinstalled and configured by the respeonsible 3rd party but are still annoying.
    The best: No other pc has trouble applying the damn gpo.
    Even the DNS resolutiom seems to work on this shit thing... :|

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 4 points 2 years ago* (1 child)

    I'd do a gpupdate /force on the client and look at the event viewer afterwards. If that doesn't turn up anything helpful, reinstalling is the most economical option.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 2 points 2 years ago

    I have tried to narrow down the cause of the issue. Since I wasn't successful I ultimately escalated the ticket to my colleague and communicated to the client that if they can't narrow it down either, we will ultimately have to do that.
    Not a pretty way to resolve the issue but sometimes it is like it is :/

    My ultimate goal with every ticket is to not just close the problem but to resolve the root cause for the long term. But that (sadly) clashes with the amount of resources a client is willing to spent.
    Solve the issue within 5min that arises every 10 days or so or solve the issue with 2 hours spent on troubleshooting and eliminating the issue

  • permalink
  • fedilink
  • source
  • parent