Confirmed in Windows Version: Windows 10 1903 Build 19030.1 and 1909.
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.
The cause is an API call to GetVolumeInformation() using a volume name from the global name space.
We had an incident open with Microsoft to correct the issue. It has now been corrected:
"The new security intelligence update version 1.305.2813.0 contains changes necessary to resolve your question relating to Image for Windows"
Issue: Image for Windows doesn't seem to start.
-
TeraByte Support
- Posts: 3624
- Joined: Thu May 05, 2011 10:37 pm
Re: Issue: Image for Windows doesn't seem to start.
I was just about to report this issue. In addition, Win10 doesn't restart. It sits on Restarting "forever".
The issue effects my UEFI computer but not the MBR computer.
The issue effects my UEFI computer but not the MBR computer.
-
Bob Coleman
- Posts: 787
- Joined: Fri Aug 12, 2011 5:58 pm
Re: Issue: Image for Windows doesn't seem to start.
TeraByte Support wrote:
> Confirmed in Windows Version: Windows 10 1930 Build 19030.1 and 1909.
I assume that should be 1903, not 1930, right?
> Confirmed in Windows Version: Windows 10 1930 Build 19030.1 and 1909.
I assume that should be 1903, not 1930, right?
-
Bob Coleman
- Posts: 787
- Joined: Fri Aug 12, 2011 5:58 pm
Re: Issue: Image for Windows doesn't seem to start.
Brian K wrote:
> I was just about to report this issue. In addition, Win10 doesn't restart.
> It sits on Restarting "forever".
>
> The issue effects my UEFI computer but not the MBR computer.
I was about to wonder why I've never seen this in either 1903 or 1909. I guess instead of wondering I'll just say that I also have not seen it on an (E)MBR computer.
> I was just about to report this issue. In addition, Win10 doesn't restart.
> It sits on Restarting "forever".
>
> The issue effects my UEFI computer but not the MBR computer.
I was about to wonder why I've never seen this in either 1903 or 1909. I guess instead of wondering I'll just say that I also have not seen it on an (E)MBR computer.
Re: Issue: Image for Windows doesn't seem to start.
For me, it only started yesterday so I think it's related to yesterday's Defender update. I've restore an image from the previous day and all is OK. But as soon as Defender updates I have the problem.
My MBR computer has the same Defender update and no IFW issue.
My UEFI tablet with 32-bit Win10 Home doesn't have the IFW issue.
My MBR computer has the same Defender update and no IFW issue.
My UEFI tablet with 32-bit Win10 Home doesn't have the IFW issue.
Re: Issue: Image for Windows doesn't seem to start.
So for me, switching off windows defender real-time protection has no effect whatsoever. Image for Windows still needs 15 minutes or more to start.
Edit: It's because disabling real-time protection in *running* Windows has no effect. However, if you start Windows without Defender (e.g. with a different antivirus protection), Image for Windows will start correctly.
Edit: It's because disabling real-time protection in *running* Windows has no effect. However, if you start Windows without Defender (e.g. with a different antivirus protection), Image for Windows will start correctly.
Re: Issue: Image for Windows doesn't seem to start.
fipsy,
My affected computer behaves differently. Win10 1909 64-bit. IFW takes 11 minutes to start. I disable Defender. Then IFW starts immediately.
My affected computer behaves differently. Win10 1909 64-bit. IFW takes 11 minutes to start. I disable Defender. Then IFW starts immediately.
-
TeraByte Support
- Posts: 3624
- Joined: Thu May 05, 2011 10:37 pm
Re: Issue: Image for Windows doesn't seem to start.
The original post has been updated.
"The new security intelligence update version 1.305.2813.0 contains changes necessary to resolve your question relating to Image for Windows"
"The new security intelligence update version 1.305.2813.0 contains changes necessary to resolve your question relating to Image for Windows"
Re: Issue: Image for Windows doesn't seem to start.
It's fixed now on my computer.
-
TeraByte Support
- Posts: 3624
- Joined: Thu May 05, 2011 10:37 pm
Re: Issue: Image for Windows doesn't seem to start.
You would have had to kill the imagew.exe or imagew64.exe process, then
start again. If you did it, then disable real-time protect, and tried
again, it wouldn't do anything since the original process is still hung up.
Anyway, they fixed it, see the original post which has been updated.
On 11/25/2019 8:20 AM, fipsy wrote:
> So for me, switching off windows defender real-time protection has no effect whatsoever. Image for Windows still needs 15 minutes or more to start.
>
> Edit: It's because disabling real-time protection in *running* Windows has no effect. However, if you start Windows without Defender (e.g. with a different antivirus protection), Image for Windows will start correctly.
>
>
start again. If you did it, then disable real-time protect, and tried
again, it wouldn't do anything since the original process is still hung up.
Anyway, they fixed it, see the original post which has been updated.
On 11/25/2019 8:20 AM, fipsy wrote:
> So for me, switching off windows defender real-time protection has no effect whatsoever. Image for Windows still needs 15 minutes or more to start.
>
> Edit: It's because disabling real-time protection in *running* Windows has no effect. However, if you start Windows without Defender (e.g. with a different antivirus protection), Image for Windows will start correctly.
>
>