Hi All,

Seems the registry hack no longer work to
bypass W11's idiot hardware requirements.

But, I found a really easy way to upgrade W10
to W11 and bypass the nonsense.

https://github.com/coofcookie/Windows11Upgrade/releases/

Worked petty cool on 21H2

HTH,
-T

T <T@invalid.invalid> posted this via news:t2le3p$trn$2@dont-email.me:

> Hi All,
>
> Seems the registry hack no longer work to
> bypass W11's idiot hardware requirements.
>
> But, I found a really easy way to upgrade W10
> to W11 and bypass the nonsense.
>
> https://github.com/coofcookie/Windows11Upgrade/releases/
>
> Worked petty cool on 21H2
>
> HTH,
> -T

Are you fuukeen serious???

Nobody in their right mind would download and install something so vague
and potentially lethal, right?

Upgrade to zombie-bot maybe.

Must be April Fools Day somewhere...

--

I AM Bucky Breeder, (*(^;

And *NO*, that is *NOT* a Jedi Light Saber I have in my pocket!

But that doesn't necessarily mean I'm happy to see you either.

On 4/6/2022 9:17 PM, T wrote:
> Hi All,
>
> Seems the registry hack no longer work to
> bypass W11's idiot hardware requirements.
>
> But, I found a really easy way to upgrade W10
> to W11 and bypass the nonsense.
>
> https://github.com/coofcookie/Windows11Upgrade/releases/
>
> Worked petty cool on 21H2
>
> HTH,
> -T
>

Did you test this on a Skylake ?

I'm curious how many curve balls you threw at it.

Is the resulting OS "Feature Complete" ?

Are you sure ?

Not that this matters of course.

Let's say the user has to do a Repair Install soon after.
Like a Microsoft troubleshooting tip recommended I do the
other day :-) Well, *of course* it didn't fix anything.
Is this installer and its Feature Complete OS,
"Repair Install proofed" ? That's what I mean by Feature
Complete, naive users are going to expect Refresh and Reset
to work.

Paul

On 4/6/22 18:47, Bucky Breeder wrote:
> T <T@invalid.invalid> posted this via news:t2le3p$trn$2@dont-email.me:
>
>> Hi All,
>>
>> Seems the registry hack no longer work to
>> bypass W11's idiot hardware requirements.
>>
>> But, I found a really easy way to upgrade W10
>> to W11 and bypass the nonsense.
>>
>> https://github.com/coofcookie/Windows11Upgrade/releases/
>>
>> Worked petty cool on 21H2
>>
>> HTH,
>> -T
>
> Are you fuukeen serious???
>
> Nobody in their right mind would download and install something so vague
> and potentially lethal, right?
>
> Upgrade to zombie-bot maybe.
>
> Must be April Fools Day somewhere...
>

Open mouth, insert foot:

https://www.virustotal.com/gui/file/989e1ee3fc93cdddfddcf85b4f8cfc85ef4d0bd2a3eefb0588a94c83d9f5ade5

On 4/6/22 19:15, Paul wrote:
> On 4/6/2022 9:17 PM, T wrote:
>> Hi All,
>>
>> Seems the registry hack no longer work to
>> bypass W11's idiot hardware requirements.
>>
>> But, I found a really easy way to upgrade W10
>> to W11 and bypass the nonsense.
>>
>> https://github.com/coofcookie/Windows11Upgrade/releases/
>>
>> Worked petty cool on 21H2
>>
>> HTH,
>> -T
>>
>
> Did you test this on a Skylake ?

Processor Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz, 1992 Mhz, 4 Core(s),
8 Logical Processor(s)

Got told wrong CPU and no TPM module

>
> I'm curious how many curve balls you threw at it.
>
> Is the resulting OS "Feature Complete" ?

Yes

> Are you sure ?
>
> Not that this matters of course.
>
> Let's say the user has to do a Repair Install soon after.
> Like a Microsoft troubleshooting tip recommended I do the
> other day :-) Well, *of course* it didn't fix anything.
> Is this installer and its Feature Complete OS,
> "Repair Install proofed" ? That's what I mean by Feature
> Complete, naive users are going to expect Refresh and Reset
> to work.

Don't really know. I have been pounding away installing
stuff

Does this help?

>sfc /scannow

Beginning system scan. This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

>Dism /Online /Cleanup-Image /RestoreHealth

Deployment Image Servicing and Management tool
Version: 10.0.22000.1

Image Version: 10.0.22000.556

[==========================100.0%==========================] The restore
operation completed successfully.
The operation completed successfully.

On 4/6/2022 10:31 PM, T wrote:
> On 4/6/22 18:47, Bucky Breeder wrote:
>> T <T@invalid.invalid> posted this via news:t2le3p$trn$2@dont-email.me:
>>
>>> Hi All,
>>>
>>> Seems the registry hack no longer work to
>>> bypass W11's idiot hardware requirements.
>>>
>>> But, I found a really easy way to upgrade W10
>>> to W11 and bypass the nonsense.
>>>
>>> https://github.com/coofcookie/Windows11Upgrade/releases/
>>>
>>> Worked petty cool on 21H2
>>>
>>> HTH,
>>> -T
>>
>> Are you fuukeen serious???
>>
>> Nobody in their right mind would download and install something so vague
>> and potentially lethal, right?
>>
>> Upgrade to zombie-bot maybe.
>>
>> Must be April Fools Day somewhere...
>>
>
>
> Open mouth, insert foot:
>
> https://www.virustotal.com/gui/file/989e1ee3fc93cdddfddcf85b4f8cfc85ef4d0bd2a3eefb0588a94c83d9f5ade5

Sometimes you have to scan the individual files, to
build a more complete picture. These could be reputational
detections for example ("not many people have downloaded the package").

https://www.virustotal.com/gui/file/d96a5211c5d78518310406368edeaf9e614fd0eddeb7673e31a583a6f61a8dd6/detection

In any case, the detections aren't exactly high quality ones.

Paul

On 4/6/22 20:13, Paul wrote:
> On 4/6/2022 10:31 PM, T wrote:
>> On 4/6/22 18:47, Bucky Breeder wrote:
>>> T <T@invalid.invalid> posted this via news:t2le3p$trn$2@dont-email.me:
>>>
>>>> Hi All,
>>>>
>>>> Seems the registry hack no longer work to
>>>> bypass W11's idiot hardware requirements.
>>>>
>>>> But, I found a really easy way to upgrade W10
>>>> to W11 and bypass the nonsense.
>>>>
>>>> https://github.com/coofcookie/Windows11Upgrade/releases/
>>>>
>>>> Worked petty cool on 21H2
>>>>
>>>> HTH,
>>>> -T
>>>
>>> Are you fuukeen serious???
>>>
>>> Nobody in their right mind would download and install something so vague
>>> and potentially lethal, right?
>>>
>>> Upgrade to zombie-bot maybe.
>>>
>>> Must be April Fools Day somewhere...
>>>
>>
>>
>> Open mouth, insert foot:
>>
>> https://www.virustotal.com/gui/file/989e1ee3fc93cdddfddcf85b4f8cfc85ef4d0bd2a3eefb0588a94c83d9f5ade5
>>
>
> Sometimes you have to scan the individual files, to
> build a more complete picture. These could be reputational
> detections for example ("not many people have downloaded the package").
>
> https://www.virustotal.com/gui/file/d96a5211c5d78518310406368edeaf9e614fd0eddeb7673e31a583a6f61a8dd6/detection
>
>
> In any case, the detections aren't exactly high quality ones.
Gee Wiz Paul. Just how many more engines does Virus
Total have to use?

>
>    Paul

On 4/6/22 20:04, T wrote:
>> Let's say the user has to do a Repair Install soon after.
>> Like a Microsoft troubleshooting tip recommended I do the
>> other day :-) Well, *of course* it didn't fix anything.
>> Is this installer and its Feature Complete OS,
>> "Repair Install proofed" ? That's what I mean by Feature
>> Complete, naive users are going to expect Refresh and Reset
>> to work.
>
> Don't really know.  I have been pounding away installing
> stuff
>
> Does this help?
>
>
> >sfc /scannow
>
> Beginning system scan.  This process will take some time.
>
> Beginning verification phase of system scan.
> Verification 100% complete.
>
> Windows Resource Protection did not find any integrity violations.
>
>
> >Dism /Online /Cleanup-Image /RestoreHealth
>
> Deployment Image Servicing and Management tool
> Version: 10.0.22000.1
>
> Image Version: 10.0.22000.556
>
> [==========================100.0%==========================] The restore
> operation completed successfully.
> The operation completed successfully.
It is currently doing the latest Windows updates. Not giving
me any grief.
2022-04 Update for Windows 11 for x64-based Systems (KB4023057)
2022-04 Cumulative Update for .NET Frameforl 3.54 ane 4.8
for Widows 11 fopr x64 (KB5009469)

Hmmmm.... X64. I thought those bozos were not
longer supporting 32 bit?

On 4/6/2022 11:40 PM, T wrote:
> On 4/6/22 20:13, Paul wrote:

>> In any case, the detections aren't exactly high quality ones.
>
> Gee Wiz Paul.  Just how many more engines does Virus
> Total have to use?

When a reputable engine states a specific malware is present

Sality23a

then we know there was a signature match, and since we know
the company that stated it (ESET or Kaspersky), it's not a
false positive cause by incompetence.

What do you think of a company that prints this on the screen ?

Malicious

It means they know fuck all about what they're doing.
That gives zero information. If I run that, will my
computer be erased ? Or will an advert appear on my screen ?
We don't know.

If you want to write on the screen:

"Warning: Reputational analysis states few people have
downloaded this software, so nobody has much
experience with it"

then that's an honest appraisal, only as far as stating
"we did not scan this" or "we cannot realistically scan this".

Companies with heuristic capability (even Malwarebytes),
their engine can at least take a stab at it, when the
sample is executed and "watched". The people who are little
better than ClamAV, really shouldn't be in Virustotal at all.
Fifty people using the exact same ClamAV signature database is
the very definition of stupid. But when you start an AV
company with "real time detection", that's how many of them
start out.

Some even started out, by copying the database of a competitor,
and they didn't even bother with ClamAV :-) Now that's clever.

Paul

On 4/6/22 22:09, Paul wrote:
> On 4/6/2022 11:40 PM, T wrote:
>> On 4/6/22 20:13, Paul wrote:
>
>>> In any case, the detections aren't exactly high quality ones.
>>
>> Gee Wiz Paul.  Just how many more engines does Virus
>> Total have to use?
>
> When a reputable engine states a specific malware is present
>
>    Sality23a
>
> then we know there was a signature match, and since we know
> the company that stated it (ESET or Kaspersky), it's not a
> false positive cause by incompetence.
>
> What do you think of a company that prints this on the screen ?
>
>    Malicious
>
> It means they know fuck all about what they're doing.
> That gives zero information. If I run that, will my
> computer be erased ? Or will an advert appear on my screen ?
> We don't know.
>
> If you want to write on the screen:
>
>    "Warning: Reputational analysis states few people have
>              downloaded this software, so nobody has much
>              experience with it"
>
> then that's an honest appraisal, only as far as stating
> "we did not scan this" or "we cannot realistically scan this".
>
> Companies with heuristic capability (even Malwarebytes),
> their engine can at least take a stab at it, when the
> sample is executed and "watched". The people who are little
> better than ClamAV, really shouldn't be in Virustotal at all.
> Fifty people using the exact same ClamAV signature database is
> the very definition of stupid. But when you start an AV
> company with "real time detection", that's how many of them
> start out.
>
> Some even started out, by copying the database of a competitor,
> and they didn't even bother with ClamAV :-) Now that's clever.
>
>    Paul
ESET Endpoint is running on the machine and it
passed it, both before and after W11 was installed.
I can't be much safer than that.

T <T@invalid.invalid> wrote:
> On 4/6/22 18:47, Bucky Breeder wrote:
>> T <T@invalid.invalid> posted this via news:t2le3p$trn$2@dont-email.me:
>>
>>> Hi All,
>>>
>>> Seems the registry hack no longer work to
>>> bypass W11's idiot hardware requirements.
>>>
>>> But, I found a really easy way to upgrade W10
>>> to W11 and bypass the nonsense.
>>>
>>> https://github.com/coofcookie/Windows11Upgrade/releases/
>>>
>>> Worked petty cool on 21H2
>>>
>>> HTH,
>>> -T
>>
>> Are you fuukeen serious???
>>
>> Nobody in their right mind would download and install something so vague
>> and potentially lethal, right?
>>
>> Upgrade to zombie-bot maybe.
>>
>> Must be April Fools Day somewhere...
>>
>
>
> Open mouth, insert foot:
>
> https://www.virustotal.com/gui/file/989e1ee3fc93cdddfddcf85b4f8cfc85ef4d0bd2a3eefb0588a94c83d9f5ade5

It's a trojan. What exactly are you trying to show? What idiot you are?

In article <t2lo7r$mpg$1@dont-email.me>, T@invalid.invalid (T) wrote:

> *From:* T <T@invalid.invalid>
> *Date:* Wed, 6 Apr 2022 21:10:34 -0700
>
> On 4/6/22 20:04, T wrote:
> >> Let's�say�the�user�has�to�do�a�Repair�Install�soon�after.
> >> Like�a�Microsoft�troubleshooting�tip�recommended�I�do�the
> >> other�day :-)�Well, *of�course*�it�didn't�fix�anything.
> >> Is�this�installer�and�its�Feature�Complete�OS,
> >> "Repair�Install�proofed"�?�That's�what�I�mean�by�Feature
> >> Complete,�naive�users�are�going�to�expect�Refresh�and�Reset
> >> to�work.
> >
> > Don't�really�know.��I�have�been�pounding�away�installing
> > stuff
> >
> > Does�this�help?
> >
> >
> > >sfc�/scannow
> >
> > Beginning�system�scan.��This�process�will�take�some�time.
> >
> > Beginning�verification�phase�of�system�scan.
> > Verification�100%�complete.
> >
> > Windows�Resource�Protection�did�not�find�any�integrity�violations.
> >
> >
> > >Dism�/Online�/Cleanup-Image�/RestoreHealth
> >
> > Deployment�Image�Servicing�and�Management�tool
> > Version:�10.0.22000.1
> >
> > Image�Version:�10.0.22000.556
> >
> > [==========================100.0%==========================] The
> > restore operation�completed�successfully.
> > The�operation�completed�successfully.
>
> It is currently doing the latest Windows updates. Not giving
> me any grief.
>
> 2022-04 Update for Windows 11 for x64-based Systems (KB4023057)
>
> 2022-04 Cumulative Update for .NET Frameforl 3.54 ane 4.8
> for Widows 11 fopr x64 (KB5009469)
It's worth reading this article from The Register:
https://tinyurl.com/p9p4hs7j

Although it currently only applies to the release preview versions, who's to say
that it won't be added to production versions of W11 in time. There's no technical
reason why MS couldn't prevent windows updates in future if W11 was found to be
running on incompatible hardware.
--
Regards
John

On 2022-04-06 11:10 p.m., T wrote:
> On 4/6/22 20:04, T wrote:
>>> Let's say the user has to do a Repair Install soon after.
>>> Like a Microsoft troubleshooting tip recommended I do the
>>> other day :-) Well, *of course* it didn't fix anything.
>>> Is this installer and its Feature Complete OS,
>>> "Repair Install proofed" ? That's what I mean by Feature
>>> Complete, naive users are going to expect Refresh and Reset
>>> to work.
>>
>> Don't really know.  I have been pounding away installing
>> stuff
>>
>> Does this help?
>>
>>
>>  >sfc /scannow
>>
>> Beginning system scan.  This process will take some time.
>>
>> Beginning verification phase of system scan.
>> Verification 100% complete.
>>
>> Windows Resource Protection did not find any integrity violations.
>>
>>
>>  >Dism /Online /Cleanup-Image /RestoreHealth
>>
>> Deployment Image Servicing and Management tool
>> Version: 10.0.22000.1
>>
>> Image Version: 10.0.22000.556
>>
>> [==========================100.0%==========================] The
>> restore operation completed successfully.
>> The operation completed successfully.
>
> It is currently doing the latest Windows updates.  Not giving
> me any grief.
>
> 2022-04 Update for Windows 11 for x64-based Systems (KB4023057)
>
> 2022-04 Cumulative Update for .NET Frameforl 3.54 ane 4.8
> for Widows 11 fopr x64 (KB5009469)
>
>
> Hmmmm.... X64.  I thought those bozos were not
> longer supporting 32 bit?

Coofcookie!!! That's enough to make you_barf_ right there.

Rene

Paul <nospam@needed.invalid> posted this via
news:t2lktu$6ig$1@dont-email.me:

> On 4/6/2022 10:31 PM, T wrote:
>> On 4/6/22 18:47, Bucky Breeder wrote:
>>> T <T@invalid.invalid> posted this via news:t2le3p$trn$2@dont-email.me:
>>>
>>>> Hi All,
>>>>
>>>> Seems the registry hack no longer work to
>>>> bypass W11's idiot hardware requirements.
>>>>
>>>> But, I found a really easy way to upgrade W10
>>>> to W11 and bypass the nonsense.
>>>>
>>>> https://github.com/coofcookie/Windows11Upgrade/releases/
>>>>
>>>> Worked petty cool on 21H2
>>>>
>>>> HTH,
>>>> -T
>>>
>>> Are you fuukeen serious???
>>>
>>> Nobody in their right mind would download and install something so
>>> vague and potentially lethal, right?
>>>
>>> Upgrade to zombie-bot maybe.
>>>
>>> Must be April Fools Day somewhere...
>>>
>>
>>
>> Open mouth, insert foot:
>>
>> https://www.virustotal.com/gui/file/989e1ee3fc93cdddfddcf85b4f8cfc85ef4d
>> 0bd2a3eefb0588a94c83d9f5ade5
>
> Sometimes you have to scan the individual files, to
> build a more complete picture. These could be reputational
> detections for example ("not many people have downloaded the package").
>
> https://www.virustotal.com/gui/file/d96a5211c5d78518310406368edeaf9e614fd
> 0eddeb7673e31a583a6f61a8dd6/detection
>
> In any case, the detections aren't exactly high quality ones.
>
> Paul

That package contains .dll files... "Dynamic Link Library". OMG! Just
because they don't trigger an alert on a malware scan does NOT mean they
don't have cloaked code... or open the door for future intrusions...

Malware attacks are *NOT* always linear processes anymore. Quite often
they are asymetrical, staggered, and implemented in progressive steps...
tiny leetle baby steps... quietly slipping-in or deleting or modifying a
line of code here, a line of code there, another line of code over there,
until suddenly ~*BAM*~, you're a zombie bot! A zombie bot who doesn't
remain operational to jabber about it; muchless make ironic snarky remarks
about foot-in-mouth disorders when they probably have zombie toes tickling
their tonsils.

IIRC, by default in order to launch your Windows 10 OS, your computer does
a server side check with the MSFT mothership for verification and
authenticity purposes... then the ubiquitous mothership "scans" and hashes
your computer for updates, upgrades, hotfixes, little doo-dads that you
might be interested in purchasing, etc....

Even *IF* "someone" could hack their way into an upgrade to Windows 11 on
an ineligble computer... Then *what*??? Trick MSFT into believing it's a
verified and authentic OS???

Totally run the thing off-line all the time???

Sounds like more trouble than it's worth.

--

I AM Bucky Breeder, (*(^;

And *NO*, that is *NOT* a Jedi Light Saber I have in my pocket!

But that doesn't necessarily mean I'm happy to see you either.

On 2022-04-07, T <T@invalid.invalid> wrote:
> Seems the registry hack no longer work to
> bypass W11's idiot hardware requirements.
>
> But, I found a really easy way to upgrade W10

Why go to any bother at all just to install Microsoft's latest
advertising delivery platform?

--
------------------------------------------------------------------------------
18 Reasons I won't be vaccinated -- https://tinyurl.com/ebty2dx3
Covid vaccines: experimental biology -- https://tinyurl.com/57mncfm5
The fraud of "Climate Change" -- https://RealClimateScience.com
There is no "climate crisis" -- https://climatedepot.com
Don't talk to cops! -- https://DontTalkToCops.com
------------------------------------------------------------------------------

On 2022-04-07 10:03 a.m., Roger Blake wrote:
> On 2022-04-07, T <T@invalid.invalid> wrote:
>> Seems the registry hack no longer work to
>> bypass W11's idiot hardware requirements.
>>
>> But, I found a really easy way to upgrade W10
>
> Why go to any bother at all just to install Microsoft's latest
> advertising delivery platform?
>

Because he likes doing things the hard way :-)

Rene

T wrote:

> Seems the registry hack no longer work to bypass W11's idiot hardware
> requirements. But, I found a really easy way to upgrade W10 to W11
> and bypass the nonsense.
>
> https://github.com/coofcookie/Windows11Upgrade/releases/

Some info on project home page (rather than pointing to code page):

https://github.com/coofcookie/Windows11Upgrade
It's donationware using crypto currency.
The project was started Oct 21, 2021, with an initial release of 1.0.0,
and it's still at that version.

Since it is open source, odd the readme.cmd file, which the home page
shows, doesn't describe just how this works. Their wiki page just
points back to the project home page. There are some issues:

https://github.com/coofcookie/Windows11Upgrade/issues?q=is%3Aissue
Some open (green), some closed (purple).

Your sure you get a non-virtualized install of Windows 11 (as an upgrade
from Windows 10)? From:

https://github.com/coofcookie/Windows11Upgrade/blob/1.0.0/Windows11Upgrade/win11_installSystem.cs#L13-L28

Looks like Virtual Desktop is getting used to wrap the Win11 installer.
I also see it is defining the following registry key:

AllowUpgradesWithUnsupportedTPMOrCPU

That's the old registry hack, as noted at:

https://support.microsoft.com/en-us/windows/ways-to-install-windows-11-e0edbbfb-cfc5-4011-868b-2ce77ac7c70e

But you claim Microsoft now bypassed that workaround. I didn't delve
further into how this program works, but it looks like it just uses the
old hacks already known.

Roger Blake wrote:
> On 2022-04-07, T <T@invalid.invalid> wrote:
>> Seems the registry hack no longer work to
>> bypass W11's idiot hardware requirements.
>>
>> But, I found a really easy way to upgrade W10
>
> Why go to any bother at all just to install Microsoft's latest
> advertising delivery platform?
>
Ensures return visits to the customer to tweak, patch, repair in the
future <gdr>

--
....w¡ñ§±¤ñ

On 4/6/2022 11:04 PM, T wrote:
> On 4/6/22 19:15, Paul wrote:
>> On 4/6/2022 9:17 PM, T wrote:
>>> Hi All,
>>>
>>> Seems the registry hack no longer work to
>>> bypass W11's idiot hardware requirements.
>>>
>>> But, I found a really easy way to upgrade W10
>>> to W11 and bypass the nonsense.
>>>
>>> https://github.com/coofcookie/Windows11Upgrade/releases/
>>>
>>> Worked petty cool on 21H2
>>>
>>> HTH,
>>> -T
>>>
>>
>> Did you test this on a Skylake ?
>
> Processor    Intel(R) Core(TM) i7-8565U CPU @ 1.80GHz, 1992 Mhz, 4 Core(s), 8 Logical Processor(s)
>
> Got told wrong CPU and no TPM module
>
>>
>> I'm curious how many curve balls you threw at it.
>>
>> Is the resulting OS "Feature Complete" ?
>
> Yes
>
>> Are you sure ?
>>
>> Not that this matters of course.
>>
>> Let's say the user has to do a Repair Install soon after.
>> Like a Microsoft troubleshooting tip recommended I do the
>> other day :-) Well, *of course* it didn't fix anything.
>> Is this installer and its Feature Complete OS,
>> "Repair Install proofed" ? That's what I mean by Feature
>> Complete, naive users are going to expect Refresh and Reset
>> to work.
>
> Don't really know.  I have been pounding away installing
> stuff
>
> Does this help?
>
>
> >sfc /scannow
>
> Beginning system scan.  This process will take some time.
>
> Beginning verification phase of system scan.
> Verification 100% complete.
>
> Windows Resource Protection did not find any integrity violations.
>
>
> >Dism /Online /Cleanup-Image /RestoreHealth
>
> Deployment Image Servicing and Management tool
> Version: 10.0.22000.1
>
> Image Version: 10.0.22000.556
>
> [==========================100.0%==========================] The restore operation completed successfully.
> The operation completed successfully.
>

My laptop is not current generation hardware (AMD V120 from 2010).
The laptop had 3GB of memory, Windows 11 real min is closer
to 2.6GB, the recommended min is 4GB. The graphics driver
for the HD4200 graphics is not even close to WDDM 3.0.

The Windows11Upgrade utility did the install of Windows 11 over
Windows 10 on the laptop. For a gutless laptop, it helps to pull
the network cable at some point, or the machine overwhelms itself
with memory compressor activity. Windows Update activity can
compete with the Windows11Upgrade for cycles.

After the install was finished (and all my applications still
peppered the desktop), I ran a "Reset" from Settings. That worked
too. The "Appraiser" thingy did not seem to be involved during
the Reset, which is a bit strange. As it was a Reset, all my
utilities were removed.

*******

During the test install, a Command Prompt window repeatedly flashes
on the screen. On a powerful machine, you might not be able
to read the Command Prompt contents. But what the Upgrade utility
is doing, is slapping around the "Appraiser" thing repeatedly, to
prevent it from running. And the system may be attempting to repair
it. I presume this is part of the warfare between the developer
and Microsoft. Microsoft probably only started repairing it, when
discovering that people were screwing with it. So that's part
of the evidence, of at least part of the approach. The file in
question, is in one of the two C:\$Windows directories.

I didn't bother to read the source. The source routine names
seemed to suggest a package level manipulation, and that's
why I was assuming a Reset could break. But maybe most of the
code in there is a smoke screen (it's an emulation of how you
pull down packages from the server, to fake a network upgrade).
But the flashing of Command Prompt windows, indicates at least
one important part of defeating the checks.

My laptop is not even remotely close to being suitable
for this (single core, 2.2GHz), and was just as far off for Windows 10.

The original contents have now been restored.

Paul

On 4/7/22 07:55, Bucky Breeder wrote:
> Paul <nospam@needed.invalid> posted this via
> news:t2lktu$6ig$1@dont-email.me:
>
>> On 4/6/2022 10:31 PM, T wrote:
>>> On 4/6/22 18:47, Bucky Breeder wrote:
>>>> T <T@invalid.invalid> posted this via news:t2le3p$trn$2@dont-email.me:
>>>>
>>>>> Hi All,
>>>>>
>>>>> Seems the registry hack no longer work to
>>>>> bypass W11's idiot hardware requirements.
>>>>>
>>>>> But, I found a really easy way to upgrade W10
>>>>> to W11 and bypass the nonsense.
>>>>>
>>>>> https://github.com/coofcookie/Windows11Upgrade/releases/
>>>>>
>>>>> Worked petty cool on 21H2
>>>>>
>>>>> HTH,
>>>>> -T
>>>>
>>>> Are you fuukeen serious???
>>>>
>>>> Nobody in their right mind would download and install something so
>>>> vague and potentially lethal, right?
>>>>
>>>> Upgrade to zombie-bot maybe.
>>>>
>>>> Must be April Fools Day somewhere...
>>>>
>>>
>>>
>>> Open mouth, insert foot:
>>>
>>> https://www.virustotal.com/gui/file/989e1ee3fc93cdddfddcf85b4f8cfc85ef4d
>>> 0bd2a3eefb0588a94c83d9f5ade5
>>
>> Sometimes you have to scan the individual files, to
>> build a more complete picture. These could be reputational
>> detections for example ("not many people have downloaded the package").
>>
>> https://www.virustotal.com/gui/file/d96a5211c5d78518310406368edeaf9e614fd
>> 0eddeb7673e31a583a6f61a8dd6/detection
>>
>> In any case, the detections aren't exactly high quality ones.
>>
>> Paul
>
> That package contains .dll files... "Dynamic Link Library". OMG! Just
> because they don't trigger an alert on a malware scan does NOT mean they
> don't have cloaked code... or open the door for future intrusions...
>
> Malware attacks are *NOT* always linear processes anymore. Quite often
> they are asymetrical, staggered, and implemented in progressive steps...
> tiny leetle baby steps... quietly slipping-in or deleting or modifying a
> line of code here, a line of code there, another line of code over there,
> until suddenly ~*BAM*~, you're a zombie bot! A zombie bot who doesn't
> remain operational to jabber about it; muchless make ironic snarky remarks
> about foot-in-mouth disorders when they probably have zombie toes tickling
> their tonsils.
>
> IIRC, by default in order to launch your Windows 10 OS, your computer does
> a server side check with the MSFT mothership for verification and
> authenticity purposes... then the ubiquitous mothership "scans" and hashes
> your computer for updates, upgrades, hotfixes, little doo-dads that you
> might be interested in purchasing, etc....
>
> Even *IF* "someone" could hack their way into an upgrade to Windows 11 on
> an ineligble computer... Then *what*??? Trick MSFT into believing it's a
> verified and authentic OS???
>
> Totally run the thing off-line all the time???
>
> Sounds like more trouble than it's worth.
>

The problem is caused by what is called "DLL side-loading".
This does not happen if you download straight from VideoLan.

This is also an issue *WITH ANY* app you download from a
third part site.

And virustotal does check the dll's too.

On 4/7/22 04:16, John K.Eason wrote:
> It's worth reading this article from The Register:
> https://tinyurl.com/p9p4hs7j

Good article.

> Although it currently only applies to the release preview versions, who's to say
> that it won't be added to production versions of W11 in time. There's no technical
> reason why MS couldn't prevent windows updates in future if W11 was found to be
> running on incompatible hardware.

Ya, that is the case. I don't see it happening though.
This is a case of FUD (fear, uncertainty, doubt). If
and when the time EVER comes, which I doubt, users
will have sufficient warning to dump their perfectly
functional hardware for something new.

M$ seriously deserves a class action suit over this.

On 4/7/22 08:03, Roger Blake wrote:
> On 2022-04-07, T <T@invalid.invalid> wrote:
>> Seems the registry hack no longer work to
>> bypass W11's idiot hardware requirements.
>>
>> But, I found a really easy way to upgrade W10
>
> Why go to any bother at all just to install Microsoft's latest
> advertising delivery platform?
>

Because far superior platforms, such as Fedora and
Mac OS, do not have the voluminous software
applications available that Windows has.

The users, except for us nerds, DO NOT CARE what
operating system they are running and seldom
even know what it is. They ONLY care if the
s*** run on it or not.

So, damn ...

I use Fedora myself. I rather enjoy it. It is
a lot closer to the CPU than Windows. And EVERYTHING
is configurable.

And I would not have a job without M$ crappy quality.

On 4/7/22 08:16, Rene Lamontagne wrote:
> On 2022-04-07 10:03 a.m., Roger Blake wrote:
>> On 2022-04-07, T <T@invalid.invalid> wrote:
>>> Seems the registry hack no longer work to
>>> bypass W11's idiot hardware requirements.
>>>
>>> But, I found a really easy way to upgrade W10
>>
>> Why go to any bother at all just to install Microsoft's latest
>> advertising delivery platform?
>>
>
> Because he likes doing things the hard way  :-)
>
> Rene
>
Its a living:
https://www.youtube.com/watch?v=pyxJ7GKGFG0

On 4/7/22 10:42, ...w¡ñ§±¤ñ wrote:
> Roger Blake wrote:
>> On 2022-04-07, T <T@invalid.invalid> wrote:
>>> Seems the registry hack no longer work to
>>> bypass W11's idiot hardware requirements.
>>>
>>> But, I found a really easy way to upgrade W10
>>
>> Why go to any bother at all just to install Microsoft's latest
>> advertising delivery platform?
>>
> Ensures return visits to the customer to tweak, patch, repair in the
> future <gdr>
>
Ya. No fooling.
Plus I get to write you guys all the time!

On 4/7/22 09:58, VanguardLH wrote:
> But you claim Microsoft now bypassed that workaround. I didn't delve
> further into how this program works, but it looks like it just uses the
> old hacks already known.

For upgrading an existing W10 system in place.

I have yet to check is a blank install works
with the hack.