Groups | Search | Server Info | Login | Register
Groups > alt.comp.os.windows-10 > #122354
| From | Roger Mills <watt.tyler@gmail.com> |
|---|---|
| Newsgroups | alt.comp.os.windows-10 |
| Subject | Re: Registry - this can't be good |
| Date | 2020-09-20 16:44 +0100 |
| Organization | Association of Revolting Peasants |
| Message-ID | <hspbmhFe51uU1@mid.individual.net> (permalink) |
| References | <hspaumFe0faU1@mid.individual.net> |
On 20/09/2020 16:31, s|b wrote: > So I'm visiting my sister and as usual I take a look at her PC (Windows > 10, all recent updates), mostly to update old software. Her C: drive was > all clogged up, a folder (Software) that I use has miraculously > vanished, Fortnite was installed, ... At his point, I'm happy Chrome > isn't installed (again). > > Then I look at the Registry and I see this: > <https://i.postimg.cc/W3TGJbdK/regedit.png> > > That can't be good, right? Avast can't find anything. CCleaner doesn't > show me these files and SUPERAntiSpyware and Malwarebytes don't raise an > alarm either. > > What could this be? The most recent backup image (Macrium) is dated > 2018, but I'm inclined to use it to get rid of this crap... unless > anyone else has a better idea? > I've no idea what caused it, but over-writing the whole dick from a very old backup sounds a bit extreme. Can't you find any more recent Restore Points, which would enable the registry to be restored to an earlier state. If there are several, start with the most recent and keep going back until this crap disappears. -- Cheers, Roger
Back to alt.comp.os.windows-10 | Previous | Next — Previous in thread | Next in thread | Find similar
Registry - this can't be good "s|b" <me@privacy.invalid> - 2020-09-20 17:31 +0200
Re: Registry - this can't be good Roger Mills <watt.tyler@gmail.com> - 2020-09-20 16:44 +0100
Re: Registry - this can't be good Ken Blake <ken@invalidemail.com> - 2020-09-20 09:39 -0700
Re: Registry - this can't be good Char Jackson <none@none.invalid> - 2020-09-20 12:18 -0500
Re: Registry - this can't be good Arlen Holder <arlen_holder@newmachines.com> - 2020-09-20 17:50 +0000
Re: Registry - this can't be good Arlen Holder <arlen_holder@newmachines.com> - 2020-09-20 18:02 +0000
Re: Registry - this can't be good Arlen Holder <arlen_holder@newmachines.com> - 2020-09-20 18:30 +0000
Re: Registry - this can't be good VanguardLH <V@nguard.LH> - 2020-09-20 13:30 -0500
Re: Registry - this can't be good Ken Blake <ken@invalidemail.com> - 2020-09-20 12:21 -0700
Re: Registry - this can't be good "s|b" <me@privacy.invalid> - 2020-09-20 21:41 +0200
Re: Registry - this can't be good Mike Easter <MikeE@ster.invalid> - 2020-09-20 12:57 -0700
Re: Registry - this can't be good Arlen Holder <arlen_holder@newmachines.com> - 2020-09-20 21:06 +0000
Re: Registry - this can't be good Arlen Holder <arlen_holder@newmachines.com> - 2020-09-20 21:08 +0000
Re: Registry - this can't be good Arlen Holder <arlen_holder@newmachines.com> - 2020-09-20 22:10 +0000
Re: Registry - this can't be good "s|b" <me@privacy.invalid> - 2020-09-22 21:54 +0200
Re: Registry - this can't be good Paul <nospam@needed.invalid> - 2020-09-22 18:06 -0400
Re: Registry - this can't be good "s|b" <me@privacy.invalid> - 2020-09-24 17:24 +0200
Re: Registry - this can't be good "s|b" <me@privacy.invalid> - 2020-09-21 22:06 +0200
Re: Registry - this can't be good Brian Gregory <void-invalid-dead-dontuse@email.invalid> - 2020-09-23 01:14 +0100
Re: Registry - this can't be good Char Jackson <none@none.invalid> - 2020-09-22 19:47 -0500
Re: Registry - this can't be good Frank Slootweg <this@ddress.is.invalid> - 2020-09-23 15:27 +0000
Re: Registry - this can't be good "s|b" <me@privacy.invalid> - 2020-09-24 17:26 +0200
Re: Registry - this can't be good Neil <neil@myplaceofwork.com> - 2020-09-20 12:04 -0400
Re: Registry - this can't be good Arlen Holder <arlen_holder@newmachines.com> - 2020-09-20 17:27 +0000
Re: Registry - this can't be good "s|b" <me@privacy.invalid> - 2020-09-21 22:10 +0200
Re: Registry - this can't be good Neil <neil@myplaceofwork.com> - 2020-09-22 07:13 -0400
Re: Registry - this can't be good "s|b" <me@privacy.invalid> - 2020-09-22 21:57 +0200
Re: Registry - this can't be good Neil <neil@myplaceofwork.com> - 2020-09-22 21:35 -0400
Re: Registry - this can't be good Brian Gregory <void-invalid-dead-dontuse@email.invalid> - 2020-09-23 01:15 +0100
Re: Registry - this can't be good "s|b" <me@privacy.invalid> - 2020-09-24 17:28 +0200
Re: Registry - this can't be good Neil <neil@myplaceofwork.com> - 2020-09-24 15:16 -0400
Re: Registry - this can't be good Paul <nospam@needed.invalid> - 2020-09-24 18:46 -0400
Re: Registry - this can't be good Brian Gregory <void-invalid-dead-dontuse@email.invalid> - 2020-09-23 01:20 +0100
Re: Registry - this can't be good VanguardLH <V@nguard.LH> - 2020-09-20 13:28 -0500
Re: Registry - this can't be good Paul <nospam@needed.invalid> - 2020-09-20 16:48 -0400
Re: Registry - this can't be good Arlen Holder <arlen_holder@newmachines.com> - 2020-09-20 22:10 +0000
Re: Registry - this can't be good Paul <nospam@needed.invalid> - 2020-09-20 21:53 -0400
Re: Registry - this can't be good Arlen Holder <arlen_holder@newmachines.com> - 2020-09-21 03:20 +0000
Re: Registry - this can't be good Paul <nospam@needed.invalid> - 2020-09-21 01:13 -0400
Re: Registry - this can't be good Shadow <Sh@dow.br> - 2020-09-20 18:50 -0300
csiph-web