Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.comp.os.windows-10 > #193604

Re: Can't get past bitlocker.

From rbowman <bowman@montana.com>
Newsgroups alt.comp.os.windows-10, alt.comp.os.windows-11
Subject Re: Can't get past bitlocker.
Date 2026-05-20 16:25 +0000
Message-ID <n765k4Fe1m1U3@mid.individual.net> (permalink)
References <r8hp0l1ic4pauec3kvua5phdp1nl2uecei@4ax.com> <n74mffF70kqU3@mid.individual.net> <10ujiol$3p4gf$1@dont-email.me>

Cross-posted to 2 groups.

Show all headers | View raw

On Wed, 20 May 2026 02:01:56 -0400, Paul wrote:

> And this is when you discover the backup/restore system doesn't have
> enough bandwidth. The restores are usually good for "onesey/twosey
> restores", but when every disk in the company needs to be paved, it was
> never designed for that style of disaster recovery.

It was painful. The division I worked for closed down and we'd given the 
clients a year of support to find another vendor. I agreed to stick around 
to fix any problems that came up but only fixed one obscure bug. Since it 
was only 3 months left we never bothered to restore the build machines or 
my Win 11 box. 

According to the IT guy he'd gotten a notification to apply a critical 
patch and did so. Later that day he got another notification but thought 
it applied to the one he'd already installed. I think it was the next day 
when the system was pwned.

It probably was like the Linux kernel. I've been getting a lot of kernel 
updates even on the distros that aren't on 7 as they try to stay ahead of 
the vulnerabilities. Miss one and you're ripe for the picking.

Back to alt.comp.os.windows-10 | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Can't get past bitlocker. micky <NONONOmisc07@fmguy.com> - 2026-05-19 16:33 -0400
  Re: Can't get past bitlocker. "Alan K." <alan@invalid.com> - 2026-05-19 16:54 -0400
    Re: Can't get past bitlocker. micky <NONONOmisc07@fmguy.com> - 2026-05-19 17:00 -0400
      Re: Can't get past bitlocker. Paul <nospam@needed.invalid> - 2026-05-19 17:56 -0400
        Re: Can't get past bitlocker. "Carlos E.R." <robin_listas@es.invalid> - 2026-05-20 14:17 +0200
      Re: Can't get past bitlocker. "Carlos E.R." <robin_listas@es.invalid> - 2026-05-20 00:23 +0200
        Re: Can't get past bitlocker. "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2026-05-20 20:28 +0800
          Re: Can't get past bitlocker. rbowman <bowman@montana.com> - 2026-05-20 16:14 +0000
            Re: Can't get past bitlocker. "Carlos E.R." <robin_listas@es.invalid> - 2026-05-20 20:24 +0200
            Re: Can't get past bitlocker. Paul <nospam@needed.invalid> - 2026-05-20 18:20 -0400
              Re: Can't get past bitlocker. "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2026-05-21 19:28 +0800
        Re: Can't get past bitlocker. micky <NONONOmisc07@fmguy.com> - 2026-05-20 15:59 -0400
          Re: Can't get past bitlocker. "Carlos E.R." <robin_listas@es.invalid> - 2026-05-20 22:09 +0200
          Re: Can't get past bitlocker. Paul <nospam@needed.invalid> - 2026-05-20 19:45 -0400
          Re: Can't get past bitlocker. Frank Slootweg <this@ddress.is.invalid> - 2026-05-21 20:03 +0000
  Re: Can't get past bitlocker. Hank Rogers <Hank@nospam.invalid> - 2026-05-19 18:08 -0500
    Re: Can't get past bitlocker. Paul <nospam@needed.invalid> - 2026-05-19 23:25 -0400
  Re: Can't get past bitlocker. rbowman <bowman@montana.com> - 2026-05-20 03:01 +0000
    Re: Can't get past bitlocker. Paul <nospam@needed.invalid> - 2026-05-20 02:01 -0400
      Re: Can't get past bitlocker. rbowman <bowman@montana.com> - 2026-05-20 16:25 +0000
        Re: Can't get past bitlocker. "Carlos E.R." <robin_listas@es.invalid> - 2026-05-20 20:27 +0200
          Re: Can't get past bitlocker. rbowman <bowman@montana.com> - 2026-05-20 20:24 +0000
            Re: Can't get past bitlocker. "Carlos E.R." <robin_listas@es.invalid> - 2026-05-21 08:59 +0200
              Re: Can't get past bitlocker. rbowman <bowman@montana.com> - 2026-05-21 18:12 +0000
    Re: Can't get past bitlocker. micky <NONONOmisc07@fmguy.com> - 2026-05-20 15:57 -0400
  Re: Can't get past bitlocker. Andy Burns <usenet@andyburns.uk> - 2026-05-20 07:51 +0100
    Re: Can't get past bitlocker. Paul <nospam@needed.invalid> - 2026-05-20 03:50 -0400
      Re: Can't get past bitlocker. Andy Burns <usenet@andyburns.uk> - 2026-05-20 10:57 +0100
      Re: Can't get past bitlocker. micky <NONONOmisc07@fmguy.com> - 2026-05-20 15:56 -0400
        Re: Can't get past bitlocker. rbowman <bowman@montana.com> - 2026-05-20 20:41 +0000
        Re: Can't get past bitlocker. Paul <nospam@needed.invalid> - 2026-05-20 19:58 -0400
          Re: Can't get past bitlocker. micky <NONONOmisc07@fmguy.com> - 2026-05-20 21:18 -0400
            Re: Can't get past bitlocker. Paul <nospam@needed.invalid> - 2026-05-21 15:07 -0400
    Re: Can't get past bitlocker. "Mr. Man-wai Chang" <toylet.toylet@gmail.com> - 2026-05-20 20:26 +0800
      Re: Can't get past bitlocker. "J. P. Gilliver" <G6JPG@255soft.uk> - 2026-05-20 14:40 +0100
        Re: Can't get past bitlocker. Frank Slootweg <this@ddress.is.invalid> - 2026-05-20 14:14 +0000
          Re: Can't get past bitlocker. "J. P. Gilliver" <G6JPG@255soft.uk> - 2026-05-20 18:43 +0100
    Re: Can't get past bitlocker. micky <NONONOmisc07@fmguy.com> - 2026-05-20 15:36 -0400

csiph-web