On Fri, 22 Nov 2019 22:30:43 PST, just as I was about to take a herb,
TeraByte Support disturbed my reverie and wrote:
>The latest Windows Defender Anti-Virus Real-time Protection included with Windows 10 has a bug which can cause Image for Windows to appear to not start. However, after several minutes, up to 15 or more minutes, the Image for Windows User Interface eventually shows up.
Not come across this at all. IfW starts very Client quickly here.
--
Cheers,
DrT
** Amateurs built the Ark, but professionals built the Titanic.**
Issue: Image for Windows doesn't seem to start.
-
- Posts: 787
- Joined: Fri Aug 12, 2011 5:58 pm
Re: Issue: Image for Windows doesn't seem to start.
DrTeeth wrote:
>
> Not come across this at all. IfW starts very Client quickly here.
> --
It seems to have been established above that this only happened on GPT/UEFI systems.
>
> Not come across this at all. IfW starts very Client quickly here.
> --
It seems to have been established above that this only happened on GPT/UEFI systems.
Re: Issue: Image for Windows doesn't seem to start.
Bob Coleman wrote:
> > --
> It seems to have been established above that this only happened on GPT/UEFI systems.
It happened on one UEFI system but not on another UEFI system. That's not much of a sample.
> > --
> It seems to have been established above that this only happened on GPT/UEFI systems.
It happened on one UEFI system but not on another UEFI system. That's not much of a sample.
-
- Posts: 787
- Joined: Fri Aug 12, 2011 5:58 pm
Re: Issue: Image for Windows doesn't seem to start.
Brian K wrote:
> Bob Coleman wrote:
>
> > > --
> > It seems to have been established above that this only happened on GPT/UEFI
> systems.
>
> It happened on one UEFI system but not on another UEFI system. That's not much of a
> sample.
I guess this is probably in the category of "Who cares?" at this point, but you previously said "The issue effects my UEFI computer but not the MBR computer". It appears to not have affected my MBR computer. We know that Dr. Teeth all BIOS/MBR so that seemed like a reasonable guess as to why he had never seen the issue.
> Bob Coleman wrote:
>
> > > --
> > It seems to have been established above that this only happened on GPT/UEFI
> systems.
>
> It happened on one UEFI system but not on another UEFI system. That's not much of a
> sample.
I guess this is probably in the category of "Who cares?" at this point, but you previously said "The issue effects my UEFI computer but not the MBR computer". It appears to not have affected my MBR computer. We know that Dr. Teeth all BIOS/MBR so that seemed like a reasonable guess as to why he had never seen the issue.