Edge InPrivate Mode Now Stores History (Bug)

[‪Some‪ ‪Nobody‪]

Could anyone please confirm that InPrivate mode is broken in Edge on Windows 10 10586.122 (latest version)?

This is unrelated to the "webcache" bug that was fixed 2 updates ago.

 

Steps:

1. open Edge

2. clear history

3. close Edge

4. open Edge and open InPrivate window

5. browse to microsoft.com or another site

6. check the history (it should be empty, but instead will have a record of that site)

7. close all Edge windows

8. reopen Edge

9. check the history (it should be empty, but instead will still have a record of that site)

10. check autocomplete in the address bar (it will improperly try to autocomplete that site)

 

I have this issue on both Windows 10 64-bit on a desktop and 32-bit on a tablet.

[BeerFan]

1. Open Edge

 

STOP RIGHT THERE! Why the heck would i want to do that w/ such a ###### browser?? 

 

Joking aside, I followed your steps and did not have any history shown or autocomplete entries. However, I'm running Insider build 14271, so this probably isn't very helpful.

[Jim K Global Moderator]

On 3/1/2016 at 5:24 PM, ‪Some‪ ‪Nobody‪ said:

Could anyone please confirm that InPrivate mode is broken in Edge on Windows 10 10586.122 (latest version)?

This is unrelated to the "webcache" bug that was fixed 2 updates ago.

 

Steps:

1. open Edge

2. clear history

3. close Edge

4. open Edge and open InPrivate window

5. browse to microsoft.com or another site

6. check the history (it should be empty, but instead will have a record of that site)

7. close all Edge windows

8. reopen Edge

9. check the history (it should be empty, but instead will still have a record of that site)

10. check autocomplete in the address bar (it will improperly try to autocomplete that site)

 

I have this issue on both Windows 10 64-bit on a desktop and 32-bit on a tablet.

Following those steps doesn't produce the issue you are seeing.  

 

[‪Some‪ ‪Nobody‪]

Thanks for testing. I just found several threads on reddit discussing the issue. It seems to have started with 10586.104. I just never noticed it until now. Here are some of the threads:

https://m.reddit.com/r/Windows10/comments/45fzco/warning_edge_inprivate_browsing_is_still_broken/

https://m.reddit.com/r/Windows10/comments/456o7l/edge_inprivate_just_got_worse/

https://m.reddit.com/r/windows/comments/45afbh/psa_do_not_use_microsoft_edge_for_inprivate/

 

Found a video (I'm on en-us, but same issue):

 

 

 

If anyone can provide additional confirmation or possibly report on this/get a response from Microsoft, I would appreciate it.

Edited March 3, 2016 by ‪Some‪ ‪Nobody‪

[Bamsebjørn]

I noticed it too, so I've stopped using Edge for private browsing until this is fixed.

[‪Some‪ ‪Nobody‪]

Thanks for the confirmation. I hope this can get more attention soon. I think it may have been buried under the news that the webcache inprivate bug was fixed, so no one is covering it. This new, more serious issue came with the update that fixed the webcache bug.

[helpifIcan]

I could be wrong but the history it shows at least for me is from the non private side rather then the private side.

[‪Some‪ ‪Nobody‪]

I've found another video from someone experiencing this issue: https://vid.me/SJeG

It seems that it doesn't affect all systems, as some people have reported that it impacts 1 or 2 of their devices, while others are fine.

The issue has existed since 10586.104 (where they fixed the webcache inprivate bug) and it remains a problem on the latest 10586.164.

I have clean reinstalled Edge from Powershell and the issue persists with default settings.

 

Could someone please make a news article about this in order to get more eyes on this issue?

[T3X4S]

Why dont you ask again if someone will make some noise about this - I think 6x is the charm !


 

[‪Some‪ ‪Nobody‪]

Oh, I'm sorry for the repetitive posting, T3X4S.

Edited March 13, 2016 by ‪Some‪ ‪Nobody‪

[zhangm Supervisor]

You can suggest it by submitting it as a news tip from the front page. It would be at the news staff's discretion as to whether to follow up.

 

However, I don't think it would make an article; consider that info is pretty lean. This issue affects only a limited number of users - most people would read the article and scratch their heads since they don't see it. At a glance, much fewer than half the replies on the reddit threads were actually confirmations. We don't know exactly why it happens. The people who see it see it, and the people who don't, don't. We don't know how to fix it. IMO there's just not much material for a story, especially given the many deficiencies in Edge as it is.

[‪Some‪ ‪Nobody‪]

Thanks for your reply, zhangm. I thought it could have been a natural followup to the related, recent news article here: https://www.neowin.net/news/microsoft-edge-browsers-inprivate-mode-may-not-be-as-private-as-you-thought, since it was the fix for that issue that created this one. However, I think the news staff will likely agree with you on the limited material, so I'll just leave it and hope a future update fixes it.

[‪Some‪ ‪Nobody‪]

I apologize for the double-post, but I just want to report that Microsoft has found the cause of the issue and it will be fixed in an upcoming security update:

Quote

Sounds like this is a known issue which impacts some desktop customers only when you have the page prediction setting turned off. We have a fix on the way in an upcoming security update - in the meantime turning page prediction on should work around the issue.

https://www.reddit.com/r/Windows10/comments/4avmv0/announcing_windows_10_mobile_insider_preview/d15vg1s

 

I've confirmed that this fixes the issue on my system. If anyone else is experiencing the issue, open Edge, go to Settings > View advanced settings > Enable the "Use page prediction..." setting toward the bottom.