On 5/6/23 00:04, ...winston wrote:
> T wrote:
>> On 5/3/23 21:28, ...winston wrote:
>>> T wrote:
>>>>
>>>> On a new install, re-enabling file extensions
>>>> is the second thing I do, right after disabling
>>>> fast boot.
>>>
>>> Fast Boot is a UEFI/BIOS/ option that reduces your computer boot time
>>> with initialization of a minimal set of devices required to launch
>>> active boot option.
>>>
>>> Fast Start is a Windows feature that allows a faster startup of the
>>> device after a shutdown and after the mobo boot process passes
>>> control to Windows which when enabled places the device in a
>>> hibernation state instead of a full shutdown.
>>>
>>
>>
>> You would think with the number of times I have
>> disabled it, that I'd remember the exact name
>> for it.
>
> Hope can be a fleeting, especially in moments where trouble appears.
>

A lot of the times when I troubleshoot I have
a visual memory of when I see it but I could
not tell you the exact names of them. When
I can't log in with Go To Assist, I will often
ask the customer "do you see something to
the effect of ...". It works.

Fast boot / fast start up -- an unethical feature
of Windows -- is one of them. The unethical
part is M$ setting it by default and not
making it an additional feature of shutdown
so the user can pick what they want to do.

T wrote:
> On 5/6/23 00:04, ...winston wrote:
>> T wrote:
>>> On 5/3/23 21:28, ...winston wrote:
>>>> T wrote:
>>>>>
>>>>> On a new install, re-enabling file extensions
>>>>> is the second thing I do, right after disabling
>>>>> fast boot.
>>>>
>>>> Fast Boot is a UEFI/BIOS/ option that reduces your computer boot
>>>> time with initialization of a minimal set of devices required to
>>>> launch active boot option.
>>>>
>>>> Fast Start is a Windows feature that allows a faster startup of the
>>>> device after a shutdown and after the mobo boot process passes
>>>> control to Windows which when enabled places the device in a
>>>> hibernation state instead of a full shutdown.
>>>>
>>>
>>>
>>> You would think with the number of times I have
>>> disabled it, that I'd remember the exact name
>>> for it.
>>
>> Hope can be a fleeting, especially in moments where trouble appears.
>>
>
> A lot of the times when I troubleshoot I have
> a visual memory of when I see it but I could
> not tell you the exact names of them.  When
> I can't log in with Go To Assist, I will often
> ask the customer "do you see something to
> the effect of ...".  It works.
>
> Fast boot / fast start up -- an unethical feature
> of Windows -- is one of them.  The unethical
> part is M$ setting it by default and not
> making it an additional feature of shutdown
> so the user can pick what they want to do.

Fast Boot was never a feature of Windows.

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

On 5/6/23 10:27, ...winston wrote:
> T wrote:
>> On 5/6/23 00:04, ...winston wrote:
>>> T wrote:
>>>> On 5/3/23 21:28, ...winston wrote:
>>>>> T wrote:
>>>>>>
>>>>>> On a new install, re-enabling file extensions
>>>>>> is the second thing I do, right after disabling
>>>>>> fast boot.
>>>>>
>>>>> Fast Boot is a UEFI/BIOS/ option that reduces your computer boot
>>>>> time with initialization of a minimal set of devices required to
>>>>> launch active boot option.
>>>>>
>>>>> Fast Start is a Windows feature that allows a faster startup of the
>>>>> device after a shutdown and after the mobo boot process passes
>>>>> control to Windows which when enabled places the device in a
>>>>> hibernation state instead of a full shutdown.
>>>>>
>>>>
>>>>
>>>> You would think with the number of times I have
>>>> disabled it, that I'd remember the exact name
>>>> for it.
>>>
>>> Hope can be a fleeting, especially in moments where trouble appears.
>>>
>>
>> A lot of the times when I troubleshoot I have
>> a visual memory of when I see it but I could
>> not tell you the exact names of them.  When
>> I can't log in with Go To Assist, I will often
>> ask the customer "do you see something to
>> the effect of ...".  It works.
>>
>> Fast boot / fast start up -- an unethical feature
>> of Windows -- is one of them.  The unethical
>> part is M$ setting it by default and not
>> making it an additional feature of shutdown
>> so the user can pick what they want to do.
>
> Fast Boot was never a feature of Windows.
Ahh, you missed the "/"

T wrote:
> On 5/6/23 10:27, ...winston wrote:
>> T wrote:
>>> On 5/6/23 00:04, ...winston wrote:
>>>> T wrote:
>>>>> On 5/3/23 21:28, ...winston wrote:
>>>>>> T wrote:
>>>>>>>
>>>>>>> On a new install, re-enabling file extensions
>>>>>>> is the second thing I do, right after disabling
>>>>>>> fast boot.
>>>>>>
>>>>>> Fast Boot is a UEFI/BIOS/ option that reduces your computer boot
>>>>>> time with initialization of a minimal set of devices required to
>>>>>> launch active boot option.
>>>>>>
>>>>>> Fast Start is a Windows feature that allows a faster startup of
>>>>>> the device after a shutdown and after the mobo boot process passes
>>>>>> control to Windows which when enabled places the device in a
>>>>>> hibernation state instead of a full shutdown.
>>>>>>
>>>>>
>>>>>
>>>>> You would think with the number of times I have
>>>>> disabled it, that I'd remember the exact name
>>>>> for it.
>>>>
>>>> Hope can be a fleeting, especially in moments where trouble appears.
>>>>
>>>
>>> A lot of the times when I troubleshoot I have
>>> a visual memory of when I see it but I could
>>> not tell you the exact names of them.  When
>>> I can't log in with Go To Assist, I will often
>>> ask the customer "do you see something to
>>> the effect of ...".  It works.
>>>
>>> Fast boot / fast start up -- an unethical feature
>>> of Windows -- is one of them.  The unethical
>>> part is M$ setting it by default and not
>>> making it an additional feature of shutdown
>>> so the user can pick what they want to do.
>>
>> Fast Boot was never a feature of Windows.
>
> Ahh, you missed the "/"
>

Nope.
a forward slash between two words/terms/phrases indicates the two
items have a connective or conflicting relationship.
Fast Boot and Fast Start have neither - independent, unrelated,
without correlation.

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

On 5/6/23 23:56, ...winston wrote:
> T wrote:
>> On 5/6/23 10:27, ...winston wrote:
>>> T wrote:
>>>> On 5/6/23 00:04, ...winston wrote:
>>>>> T wrote:
>>>>>> On 5/3/23 21:28, ...winston wrote:
>>>>>>> T wrote:
>>>>>>>>
>>>>>>>> On a new install, re-enabling file extensions
>>>>>>>> is the second thing I do, right after disabling
>>>>>>>> fast boot.
>>>>>>>
>>>>>>> Fast Boot is a UEFI/BIOS/ option that reduces your computer boot
>>>>>>> time with initialization of a minimal set of devices required to
>>>>>>> launch active boot option.
>>>>>>>
>>>>>>> Fast Start is a Windows feature that allows a faster startup of
>>>>>>> the device after a shutdown and after the mobo boot process
>>>>>>> passes control to Windows which when enabled places the device in
>>>>>>> a hibernation state instead of a full shutdown.
>>>>>>>
>>>>>>
>>>>>>
>>>>>> You would think with the number of times I have
>>>>>> disabled it, that I'd remember the exact name
>>>>>> for it.
>>>>>
>>>>> Hope can be a fleeting, especially in moments where trouble appears.
>>>>>
>>>>
>>>> A lot of the times when I troubleshoot I have
>>>> a visual memory of when I see it but I could
>>>> not tell you the exact names of them.  When
>>>> I can't log in with Go To Assist, I will often
>>>> ask the customer "do you see something to
>>>> the effect of ...".  It works.
>>>>
>>>> Fast boot / fast start up -- an unethical feature
>>>> of Windows -- is one of them.  The unethical
>>>> part is M$ setting it by default and not
>>>> making it an additional feature of shutdown
>>>> so the user can pick what they want to do.
>>>
>>> Fast Boot was never a feature of Windows.
>>
>> Ahh, you missed the "/"
>>
>
> Nope.
>  a forward slash between two words/terms/phrases indicates the two
> items have a connective or conflicting relationship.
>  Fast Boot and Fast Start have neither - independent, unrelated,
> without correlation.
>
Okay fanboi, no know I mix the terms up. So sue me.

T wrote:
> On 5/6/23 23:56, ...winston wrote:
>>>
>>
>> Nope.
>>   a forward slash between two words/terms/phrases indicates the two
>> items have a connective or conflicting relationship.
>>   Fast Boot and Fast Start have neither - independent, unrelated,
>> without correlation.
>>
> no know  I mix the terms up.  So sue me.

Now know!!
Wow...and admission of being wrong.
That didn't hurt too much<g>

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

On 5/7/23 15:13, ...winston wrote:
> T wrote:
>> On 5/6/23 23:56, ...winston wrote:
>>>>
>>>
>>> Nope.
>>>   a forward slash between two words/terms/phrases indicates the two
>>> items have a connective or conflicting relationship.
>>>   Fast Boot and Fast Start have neither - independent, unrelated,
>>> without correlation.
>>>
>>  no know  I mix the terms up.  So sue me.
>
> Now know!!
>  Wow...and admission of being wrong.
>  That didn't hurt too much<g>
>

When I am wrong, I stand corrected. It is
a good thing. You should try it too, fanboi.

T wrote:
> On 5/7/23 15:13, ...winston wrote:
>> T wrote:
>>> On 5/6/23 23:56, ...winston wrote:
>>>>>
>>>>
>>>> Nope.
>>>>   a forward slash between two words/terms/phrases indicates the two
>>>> items have a connective or conflicting relationship.
>>>>   Fast Boot and Fast Start have neither - independent, unrelated,
>>>> without correlation.
>>>>
>>>  no know  I mix the terms up.  So sue me.
>>
>> Now know!!
>>   Wow...and admission of being wrong.
>>   That didn't hurt too much<g>
>>
>
>
> When I am wrong, I stand corrected.  It is
> a good thing.  You should try it too, fanboi.

Batting 1-3 in owning up to 'I stand corrected'
2. Fast Startup disabled doesn't fix artifacts.
3. The latest - agreeing that 'turn off fast startup and Windows
**will reboot** is an excellent description. It's not, Windows doesn't
reboot after disabling fast startup.

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

On 5/7/23 22:32, ...winston wrote:
> T wrote:
>> On 5/7/23 15:13, ...winston wrote:
>>> T wrote:
>>>> On 5/6/23 23:56, ...winston wrote:
>>>>>>
>>>>>
>>>>> Nope.
>>>>>   a forward slash between two words/terms/phrases indicates the two
>>>>> items have a connective or conflicting relationship.
>>>>>   Fast Boot and Fast Start have neither - independent, unrelated,
>>>>> without correlation.
>>>>>
>>>>  no know  I mix the terms up.  So sue me.
>>>
>>> Now know!!
>>>   Wow...and admission of being wrong.
>>>   That didn't hurt too much<g>
>>>
>>
>>
>> When I am wrong, I stand corrected.  It is
>> a good thing.  You should try it too, fanboi.
>
> Batting 1-3 in owning up to 'I stand corrected'
>  2. Fast Startup disabled doesn't fix artifacts.
>  3. The latest - agreeing that 'turn off fast startup and Windows
> **will reboot** is an excellent description.  It's not, Windows doesn't
> reboot after disabling fast startup.
>
>
Winston,
Here is the thing Winston. You are nearly
encyclopedia in your knowledge of all things
Windows. But your have your limits as
we all do. But when you hit your wall, you are
absolutely convinced that you know what you
are doing anyway. And when that happens,
the jerk in you comes out.
For instance, disabling Fast Startup and
doing a hard reboot did get rid of artifacts.
But that can't be in your world view. Your
knowledge says it can't. And because you can't
think past your wall, you somehow think you
have just entrapped me as a fraud (the jerk part
of you I mentioned above).
And you have no freaking idea why the problem
went away and could not be reproduced. Neither
do I. I can speculate though and I present it
as speculation, not a fact as your wall states.
Ya, I know, Windows is a stable operating system
in your world view. Not in mine. I make my
living off Windows problems. I have seen it all.
And I am sure there is more to comes.
And, wonder of wonders, I can make Windows fairly
stable for a M$ operating system for my customers.
But M$ can do no wrong? Huh? Fanbio? Fast Startup
never causes any wild and weird issues, does it.
Can't be in your world view.
Also, in item three above, you are misrepresenting
me. I CLEARLY state that I do a hard reboot
after disabling fast startup.
shutdown /r /f /t 00
I never stated that Windows did it on its own
after disabling the unethical feature. If
you do not do a hard reboot, the setting
does not take.
So, Winston, when you do not know or disagree,
put your jerk in the closet and act like
a gentleman. You are very good at what
you do, but you are not perfect.
And no, you have not "entrapped" me. You have
just demonstrated that you hit your wall and
when that happens, your inner jerk comes out.
I also suspect that your personally do not like
me and that "entrapping" me is a goal of yours.
I could be wrong on that.
Your encyclopedic knowledge of Windows is the
only reason I have not put your ass in
my kill file.
--Todd

T wrote:
> On 5/7/23 22:32, ...winston wrote:
>> T wrote:
>>> On 5/7/23 15:13, ...winston wrote:
>>>> T wrote:
>>>>> On 5/6/23 23:56, ...winston wrote:
>>>>>>>
>>>>>>
>>>>>> Nope.
>>>>>>   a forward slash between two words/terms/phrases indicates the
>>>>>> two items have a connective or conflicting relationship.
>>>>>>   Fast Boot and Fast Start have neither - independent, unrelated,
>>>>>> without correlation.
>>>>>>
>>>>>  no know  I mix the terms up.  So sue me.
>>>>
>>>> Now know!!
>>>>   Wow...and admission of being wrong.
>>>>   That didn't hurt too much<g>
>>>>
>>>
>>>
>>> When I am wrong, I stand corrected.  It is
>>> a good thing.  You should try it too, fanboi.
>>
>> Batting 1-3 in owning up to 'I stand corrected'
>>   2. Fast Startup disabled doesn't fix artifacts.
>>   3. The latest - agreeing that 'turn off fast startup and Windows
>> **will reboot** is an excellent description.  It's not, Windows
>> doesn't reboot after disabling fast startup.
>>
>>
>
> Winston,
>
> Here is the thing Winston.  You are nearly
> encyclopedia in your knowledge of all things
> Windows.  But your have your limits as
> we all do.  But when you hit your wall, you are
> absolutely convinced that you know what you
> are doing anyway.  And when that happens,
> the jerk in you comes out.
>
> For instance, disabling Fast Startup and
> doing a hard reboot did get rid of artifacts.
> But that can't be in your world view. Your
> knowledge says it can't.  And because you can't
> think past your wall, you somehow think you
> have just entrapped me as a fraud (the jerk part
> of you I mentioned above).
>
> And you have no freaking idea why the problem
> went away and could not be reproduced.  Neither
> do I.  I can speculate though and I present it
> as speculation, not a fact as your wall states.
>
> Ya, I know, Windows is a stable operating system
> in your world view.  Not in mine.  I make my
> living off Windows problems. I have seen it all.
> And I am sure there is more to comes.
>
> And, wonder of wonders, I can make Windows fairly
> stable for a M$ operating system for my customers.
> But M$ can do no wrong?  Huh?  Fanbio?  Fast Startup
> never causes any wild and weird issues, does it.
> Can't be in your world view.
>
> Also, in item three above, you are misrepresenting
> me.  I CLEARLY state that I do a hard reboot
> after disabling fast startup.
>
>      shutdown /r /f /t 00
>
> I never stated that Windows did it on its own
> after disabling the unethical feature.  If
> you do not do a hard reboot, the setting
> does not take.
>
> So, Winston, when you do not know or disagree,
> put your jerk in the closet and act like
> a gentleman.  You are very good at what
> you do, but you are not perfect.
>
> And no, you have not "entrapped" me.  You have
> just demonstrated that you hit your wall and
> when that happens, your inner jerk comes out.
>
> I also suspect that your personally do not like
> me and that "entrapping" me is a goal of yours.
> I could be wrong on that.
>
> Your encyclopedic knowledge of Windows is the
> only reason I have not put your ass in
> my kill file.
>
> --Todd

No wall.
You reasoning in this case is false.
Fast Startup being disabled doesn't fix artifacts.
Windows doesn't reboot after disabling Fast Startup

Feel free to have the last word.

It's in your nature to complain about MSFT, for the most part it's
spot-on, other times your analysis and claims are without proof.
- it's easy to blame something with a preconceived position..but
there's a difference in complaining vs. accuracy.

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

On 5/8/23 13:50, ...winston wrote:
> T wrote:
>> On 5/7/23 22:32, ...winston wrote:
>>> T wrote:
>>>> On 5/7/23 15:13, ...winston wrote:
>>>>> T wrote:
>>>>>> On 5/6/23 23:56, ...winston wrote:
>>>>>>>>
>>>>>>>
>>>>>>> Nope.
>>>>>>>   a forward slash between two words/terms/phrases indicates the
>>>>>>> two items have a connective or conflicting relationship.
>>>>>>>   Fast Boot and Fast Start have neither - independent, unrelated,
>>>>>>> without correlation.
>>>>>>>
>>>>>>  no know  I mix the terms up.  So sue me.
>>>>>
>>>>> Now know!!
>>>>>   Wow...and admission of being wrong.
>>>>>   That didn't hurt too much<g>
>>>>>
>>>>
>>>>
>>>> When I am wrong, I stand corrected.  It is
>>>> a good thing.  You should try it too, fanboi.
>>>
>>> Batting 1-3 in owning up to 'I stand corrected'
>>>   2. Fast Startup disabled doesn't fix artifacts.
>>>   3. The latest - agreeing that 'turn off fast startup and Windows
>>> **will reboot** is an excellent description.  It's not, Windows
>>> doesn't reboot after disabling fast startup.
>>>
>>>
>>
>> Winston,
>>
>> Here is the thing Winston.  You are nearly
>> encyclopedia in your knowledge of all things
>> Windows.  But your have your limits as
>> we all do.  But when you hit your wall, you are
>> absolutely convinced that you know what you
>> are doing anyway.  And when that happens,
>> the jerk in you comes out.
>>
>> For instance, disabling Fast Startup and
>> doing a hard reboot did get rid of artifacts.
>> But that can't be in your world view. Your
>> knowledge says it can't.  And because you can't
>> think past your wall, you somehow think you
>> have just entrapped me as a fraud (the jerk part
>> of you I mentioned above).
>>
>> And you have no freaking idea why the problem
>> went away and could not be reproduced.  Neither
>> do I.  I can speculate though and I present it
>> as speculation, not a fact as your wall states.
>>
>> Ya, I know, Windows is a stable operating system
>> in your world view.  Not in mine.  I make my
>> living off Windows problems. I have seen it all.
>> And I am sure there is more to comes.
>>
>> And, wonder of wonders, I can make Windows fairly
>> stable for a M$ operating system for my customers.
>> But M$ can do no wrong?  Huh?  Fanbio?  Fast Startup
>> never causes any wild and weird issues, does it.
>> Can't be in your world view.
>>
>> Also, in item three above, you are misrepresenting
>> me.  I CLEARLY state that I do a hard reboot
>> after disabling fast startup.
>>
>>       shutdown /r /f /t 00
>>
>> I never stated that Windows did it on its own
>> after disabling the unethical feature.  If
>> you do not do a hard reboot, the setting
>> does not take.
>>
>> So, Winston, when you do not know or disagree,
>> put your jerk in the closet and act like
>> a gentleman.  You are very good at what
>> you do, but you are not perfect.
>>
>> And no, you have not "entrapped" me.  You have
>> just demonstrated that you hit your wall and
>> when that happens, your inner jerk comes out.
>>
>> I also suspect that your personally do not like
>> me and that "entrapping" me is a goal of yours.
>> I could be wrong on that.
>>
>> Your encyclopedic knowledge of Windows is the
>> only reason I have not put your ass in
>> my kill file.
>>
>> --Todd
>
> No wall.
>  You reasoning in this case is false.
>  Fast Startup being disabled doesn't fix artifacts.
A good reboot did. But is is necessary for you
to twist peoples words to make your point.
>  Windows doesn't reboot after disabling Fast Startup
You are twisting words again.
>
>  Feel free to have the last word.
No problem.
>  It's in your nature to complain about MSFT, for the most part it's
> spot-on, other times your analysis and claims are without proof.
>  - it's easy to blame something with a preconceived position..but
> there's a difference in complaining vs. accuracy.
You are describing yourself. And you clearly have
hit your wall and are starting to display of the
Dunning–Kruger effect, or you would not have to twist
peoples words and claim absolute knowledge over things
you have no idea about.

T <T@invalid.invalid> wrote:
> On 5/8/23 13:50, ...winston wrote:
[...]

> > No wall.
> >  You reasoning in this case is false.
> >  Fast Startup being disabled doesn't fix artifacts.
>
> A good reboot did. But is is necessary for you
> to twist peoples words to make your point.

Nope, (after disabling Fast Startup,) "A good reboot did" *not* *fix*
the artifacts.

The artifacts did (supposedly) not *reappear*. There is no proof
whatsoever that disabling Fast Startup fixed the problem, because you
never did the verification needed to provide that proof.

That you don't seem to realize the difference between a problem not
re-appearing and a problem being fixed, is quite telling.

As I mentioned before, I don't blame you for not doing the
verification, because that would probably inconvenience your customer,
but I *do* blame you for drawing baseless conclusions and especially for
abusing and insulting others who point out the errors in your 'methods'.

[...]