Edge not working

On 05/11/2018 12:54, Terry Pinnell wrote:
I assume you didn't read my reply yesterday to Ken Blake.


No. He is another idiot like you. who the **** is Ken Blake? Is he
another demented individual like you and Steve? I don't see him here.
Did you make up names or have you lost your brain completely trying to
use Windows 10?


--
With over 950 million devices now running Windows 10, customer
satisfaction is higher than any previous version of windows.

On Mon, 05 Nov 2018 09:49:06 +0000, Stephen Wolstenholme
wrote:

On Sun, 04 Nov 2018 09:54:36 -0700, Ken Blake
wrote:

On Sun, 04 Nov 2018 16:01:25 +0000, Terry Pinnell
wrote:

Trying to open Edge by any method fails. An empty window pops up only
briefly.

I've tried several suggested fixes so far in vain. Most attempts were
handicapped because I also had a freezing mouse problem. Now that's
fixed I'll repeat some 'fixes' methodically, but would appreciate any
suggestions please.




Here's my suggestion: stop trying to use Edge (the *worst* of all
available browsers, in my opinion) and switch to almost any other
browser. My personal choice is FireFox.

I agree with that. Edge is very poor. I've been using Chrome since
Google first produced it. I use bookmarks rather than shortcuts.



I'm in the great minority, I know, but as far as I'm concerned Edge is
the worst browser and Chrome is the second worst browser. It's only
slightly better than Edge.

On Sun, 04 Nov 2018 22:35:41 +0000, Terry Pinnell
wrote:

Ken Blake wrote:

On Sun, 04 Nov 2018 16:01:25 +0000, Terry Pinnell
wrote:

Trying to open Edge by any method fails. An empty window pops up only
briefly.

I've tried several suggested fixes so far in vain. Most attempts were
handicapped because I also had a freezing mouse problem. Now that's
fixed I'll repeat some 'fixes' methodically, but would appreciate any
suggestions please.




Here's my suggestion: stop trying to use Edge (the *worst* of all
available browsers, in my opinion) and switch to almost any other
browser. My personal choice is FireFox.

I don't use edge. My preferred browser is Waterfox. But the OS and some
MS apps frequently try to use Edge.


I don't know why your experience is so different from mine, but I
never run into that problem.

Paul wrote:

Ken Blake wrote:
On Sun, 04 Nov 2018 16:01:25 +0000, Terry Pinnell
wrote:

Trying to open Edge by any method fails. An empty window pops up only
briefly.

I've tried several suggested fixes so far in vain. Most attempts were
handicapped because I also had a freezing mouse problem. Now that's
fixed I'll repeat some 'fixes' methodically, but would appreciate any
suggestions please.




Here's my suggestion: stop trying to use Edge (the *worst* of all
available browsers, in my opinion) and switch to almost any other
browser. My personal choice is FireFox.

My suggestion was to try creating a new user account.

As portions of Store programs are in Appdata.
A new account means a new Appdata.

If Edge doesn't spray the Event Viewer with error 5 permission
issues while doing process isolation (containers), then you know
it's either the code portion in your current account, or the
data portion (including the Edge archive files).

One of the popular (usually factual) windows websites, suggested
deleting the folder with the code, then using the usual command
to reinstall Edge. And the reason they do it that way, is Edge
has the in-box bit set, so it's not removable (I flipped that
bit and tried to remove Edge, but all that seemed to do is
remove the icon). You cannot uninstall it and expect it to be
fully uninstalled. So what that web site was doing, is deleting
the folder, then doing a reinstall in Powershell (in your
current account).

https://www.thewindowsclub.com/reset...-in-windows-10

Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach
{Add-AppxPackage -DisableDevelopmentMode -Register
"$($_.InstallLocation)\AppXManifest.xml" -Verbose}

I can never be sure, with commands like that, where the AppXManifest.xml
is coming from... From the folder you just deleted ?

Paul

I've progressed only marginally. After various steps, including those
here
https://www.drivereasy.com/knowledge...s-10-solved/#b
Edge now comes up for a bit longer, displaying an incomplete message:
https://www.dropbox.com/s/i4cwdywfvu...ge-2.jpg?raw=1

I then tried playing with Settings Apps Apps & Features Microsoft
Edge. 'Repair' gets a promising checkmark, but trying to open Edge fails
and the icon vanishes from the taskbar. 'Reset' doesn't get it back.
Using the now familiar PS command

Get-AppXPackage -AllUsers | Foreach {Add-AppxPackage
-DisableDevelopmentMode -Register
"$($_.InstallLocation)\AppXManifest.xml"}

restores the icon and the original incorrect behaviour.

I don't like or use Edge. But as it's an integral Win 10 component, used
for example to deliver 'Help and Support', I'd like to get it working.

Terry, East Grinstead, UK

Ken Blake wrote:
On Sun, 04 Nov 2018 22:35:41 +0000, Terry Pinnell
wrote:

Ken Blake wrote:

On Sun, 04 Nov 2018 16:01:25 +0000, Terry Pinnell
wrote:

Trying to open Edge by any method fails. An empty window pops up only
briefly.

I've tried several suggested fixes so far in vain. Most attempts were
handicapped because I also had a freezing mouse problem. Now that's
fixed I'll repeat some 'fixes' methodically, but would appreciate any
suggestions please.



Here's my suggestion: stop trying to use Edge (the *worst* of all
available browsers, in my opinion) and switch to almost any other
browser. My personal choice is FireFox.
I don't use edge. My preferred browser is Waterfox. But the OS and some
MS apps frequently try to use Edge.


I don't know why your experience is so different from mine, but I
never run into that problem.

Windows Help opens stuff in MSEdge.

Cortana and her Bing searches open in MSEdge.

Even if your default browser is set to something else.

Consequently, you'd want a fully function MSEdge.
If you were hoping to get "Help", you would not want
to be further challenged by platform issues.

Paul

Paul wrote:

Terry Pinnell wrote:
VanguardLH wrote:

Terry Pinnell wrote:

Trying to open Edge by any method fails. An empty window pops up only
briefly. I've tried several suggested fixes so far in vain.
Are some of those methods included in the following?

- NOT define a home page in Edge, or use about:blank.
- Load Edge in its safe mode.
- Reset Edge.
- Load Windows 10 in its safe mode w/networking.
- Temporarily disable all non-MS anti-virus and other security software.
- Load Edge using its protocol, as in "microsoft-edge:urltosite".

The most likely source of clues might lie in this composite screenshot
of Event Viewer. Whenever an attempt is made to open Edge, Event 1000
occurs and is then repeatedly followed by 21, 37, 38 and 22.

https://www.dropbox.com/s/qx1r2zdoo9...e-1..jpg?raw=1
The appcontainer is to sandbox webapps. It was added back in Win8 for
store apps. That's why I asked if you tried starting Edge in its safe
mode to get rid of any and all extensions you installed into Edge. If
you have old extensions, especially those requiring ActiveX, they won't
run inside an appcontainer. Edge runs inside an appcontainer. Some
extensions, like Flash, are run in their own appcontainer. See:

https://blogs.windows.com/msedgedev/...-edge-sandbox/
https://docs.microsoft.com/en-us/win...iner-isolation

Since one of the errors involves CreateAppContainerProfile, looks like
an appcontainer process cannot be generated to host the Edge app. I've
found some articles that the error might be about connecting
(registering) to the Windows Firewall. Is that enabled? Users can
encounter problems even with the Start Menu or Windows taskbar if the
Window Firewall isn't working. What other non-Microsoft anti-malware or
security software have you installed?

Were you ever hit with malware? Did some security software do a
disinfection? That might remove the active components of malware but it
does NOT return the OS back to a state prior to infection. Malware can
make lots of changes that remain after it gets disinfected. Might be
time for a fresh install of the OS.

Have you yet got rid of ClassicShell? Again, as mentioned, similar to
malware, uninstalling it may not undo all the changes it made.

Anyone know how to gain the permission I asked about please?

Terry, East Grinstead, UK

I thought I put up a slide for this the other day.
Don't remember which thread though.

https://s22.postimg.cc/ktpilht29/ele..._installer.gif

Some instructions. In this post, I demonstrate deleting a 7Z EXE
file from Program Files folder. Without changing the permissions
on the item at all. Just elevating myself sufficiently. Steps
1 through 4, not the "appendix" section.



http://al.howardknight.net/msgid.cgi...nt-email.me%3E

TrustedInstaller is only available as a "token". It's not
a conventional account. It doesn't have a home directory.
It doesn't have a password. The token is "copied" from the
Windows Module Installer service. This is why one of the slides
shows me starting WMI, just before issuing a command that
needs to copy that token.

It's not really "Higher Than Administrator", but more
an issue of being "More obscure than Administrator".
"Getting the power, is half the fun."

Paul

SUCCESS! So satisfying when a couple of days' forensics ends up with an
elegant fix ;-)

This came from a post by KJSTech1 Thursday, September 28, 2017 7:31 PM
https://social.technet.microsoft.com...or-update-1703
reporting a solution found by rafaeljsc.

Summarising, you perform the PowerShell reset of Microsoft Edge

Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach
{Add-AppxPackage -DisableDevelopmentMode -Register
“$($_.InstallLocation)\AppXManifest.xml” -Verbose}

But the crucial step for me and others was to add a new Registry key,
using this elevated command prompt:

reg add "HKCU\Software\Microsoft\Internet Explorer\Spartan" /v
RAC_LaunchFlags /t REG_DWORD /d 1 /f

That fix appears about two thirds down the thread:
https://social.technet.microsoft.com...or-update-1703

I've no idea what that key does, much less how rafaeljsc discovered it.
I'd like to, but am content to have Help & Support opening again

--------------------

In case that's not the solution for others who end up here, I'll mention
some of the other stuff I found after previous posts.

I googled edgelso.dll, a file implicated in Event Viewer and non
existent on my PC and found this plainly relevant thread, describing
very similar symptoms to mine:
https://developer.microsoft.com/en-u...sues/11975881/
But the workaround (close IBM Trusteer Rapport) which was identified
about half way through comments by Paul C and confirmed by others did
not help me. I have no such program and there's no reference to it on my
PC.

Before the fix, here are the main Event Viewer events I found
immediately after the opening and brief appearance of Edge

Event ID 10010 DCOM (Many):
"The server
Microsoft.MicrosoftEdge_42.17134.1.0_neutral__8wek yb3d8bbwe!ContentProcess#{0003140C-0001-0000-2F5D-A70300000000}
did not register with DCOM within the required timeout."

Event ID 1000 Application Errors:
==================================
EMODEL.dll (Few)
Faulting application name: MicrosoftEdge.exe, version: 11.0.17134.376,
time stamp: 0x5bcc2c99
Faulting module name: EMODEL.dll, version: 11.0.17134.376, time stamp:
0x5bcc2a1f
Exception code: 0xc0000409
Fault offset: 0x0000000000190d6e
Faulting process ID: 0x66b0
Faulting application start time: 0x01d475b649cb86a7
Faulting application path:
C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wek yb3d8bbwe\MicrosoftEdge.exe
Faulting module path:
C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wek yb3d8bbwe\EMODEL.dll
Report ID: eb684595-c438-43c1-8573-c970b067ac16
Faulting package full name:
Microsoft.MicrosoftEdge_42.17134.1.0_neutral__8wek yb3d8bbwe
Faulting package-relative application ID: MicrosoftEdge


EdgeContent.dll (Many)
---------------------
Faulting application name: MicrosoftEdgeCP.exe, version: 11.0.17134.376,
time stamp: 0x5bcc2819
Faulting module name: EdgeContent.dll, version: 11.0.17134.376, time
stamp: 0xfc8bc76b
Exception code: 0xc0000409
Fault offset: 0x00000000000afc2a
Faulting process ID: 0x550
Faulting application start time: 0x01d475b64f8a75a4
Faulting application path:
C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wek yb3d8bbwe\MicrosoftEdgeCP.exe
Faulting module path: C:\WINDOWS\SYSTEM32\EdgeContent.dll
Report ID: 07d7b5e6-149d-49e8-97a6-0bf069162060
Faulting package full name:
Microsoft.MicrosoftEdge_42.17134.1.0_neutral__8wek yb3d8bbwe
Faulting package-relative application ID: ContentProcess

Terry Pinnell wrote:


SUCCESS! So satisfying when a couple of days' forensics ends up with an
elegant fix ;-)

This came from a post by KJSTech1 Thursday, September 28, 2017 7:31 PM
https://social.technet.microsoft.com...or-update-1703
reporting a solution found by rafaeljsc.

Summarising, you perform the PowerShell reset of Microsoft Edge

Get-AppXPackage -AllUsers -Name Microsoft.MicrosoftEdge | Foreach
{Add-AppxPackage -DisableDevelopmentMode -Register
“$($_.InstallLocation)\AppXManifest.xml” -Verbose}

But the crucial step for me and others was to add a new Registry key,
using this elevated command prompt:

reg add "HKCU\Software\Microsoft\Internet Explorer\Spartan" /v
RAC_LaunchFlags /t REG_DWORD /d 1 /f

That fix appears about two thirds down the thread:
https://social.technet.microsoft.com...or-update-1703

I've no idea what that key does, much less how rafaeljsc discovered it.
I'd like to, but am content to have Help & Support opening again

--------------------

In case that's not the solution for others who end up here, I'll mention
some of the other stuff I found after previous posts.

I googled edgelso.dll, a file implicated in Event Viewer and non
existent on my PC and found this plainly relevant thread, describing
very similar symptoms to mine:
https://developer.microsoft.com/en-u...sues/11975881/
But the workaround (close IBM Trusteer Rapport) which was identified
about half way through comments by Paul C and confirmed by others did
not help me. I have no such program and there's no reference to it on my
PC.

Before the fix, here are the main Event Viewer events I found
immediately after the opening and brief appearance of Edge

Event ID 10010 DCOM (Many):
"The server
Microsoft.MicrosoftEdge_42.17134.1.0_neutral__8wek yb3d8bbwe!ContentProcess#{0003140C-0001-0000-2F5D-A70300000000}
did not register with DCOM within the required timeout."

Event ID 1000 Application Errors:
==================================
EMODEL.dll (Few)
Faulting application name: MicrosoftEdge.exe, version: 11.0.17134.376,
time stamp: 0x5bcc2c99
Faulting module name: EMODEL.dll, version: 11.0.17134.376, time stamp:
0x5bcc2a1f
Exception code: 0xc0000409
Fault offset: 0x0000000000190d6e
Faulting process ID: 0x66b0
Faulting application start time: 0x01d475b649cb86a7
Faulting application path:
C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wek yb3d8bbwe\MicrosoftEdge.exe
Faulting module path:
C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wek yb3d8bbwe\EMODEL.dll
Report ID: eb684595-c438-43c1-8573-c970b067ac16
Faulting package full name:
Microsoft.MicrosoftEdge_42.17134.1.0_neutral__8wek yb3d8bbwe
Faulting package-relative application ID: MicrosoftEdge


EdgeContent.dll (Many)
---------------------
Faulting application name: MicrosoftEdgeCP.exe, version: 11.0.17134.376,
time stamp: 0x5bcc2819
Faulting module name: EdgeContent.dll, version: 11.0.17134.376, time
stamp: 0xfc8bc76b
Exception code: 0xc0000409
Fault offset: 0x00000000000afc2a
Faulting process ID: 0x550
Faulting application start time: 0x01d475b64f8a75a4
Faulting application path:
C:\Windows\SystemApps\Microsoft.MicrosoftEdge_8wek yb3d8bbwe\MicrosoftEdgeCP.exe
Faulting module path: C:\WINDOWS\SYSTEM32\EdgeContent.dll
Report ID: 07d7b5e6-149d-49e8-97a6-0bf069162060
Faulting package full name:
Microsoft.MicrosoftEdge_42.17134.1.0_neutral__8wek yb3d8bbwe
Faulting package-relative application ID: ContentProcess

https://borncity.com/win/2017/09/26/...re-or-crashes/

A commenter there mentions that "RAC_LaunchFlags" was present
on a previous Win10 release, and it doesn't get migrated
properly. Still no mention of exactly what it does.

The 17134 I just installed via the RecoveryDrive experiment,
doesn't have that key either. I've not had any visible problems
with Edge similar to the ones you've had.

I wonder if the reinstall actually does anything, and it's
that registry setting that is helping ?

In another thread, instead of using command line, there
was mention of a mechanism in Apps, to reset/reinstall an app.
I've shut down my Win10 right now, and won't be booting to
check that out :-) I've hit my boot limit for Win10 at
the moment, after many many boot cycles :-)

I wonder if Microsoft will ever be able to shed the
feeling of "Beta Software" ? A permanent Beta. We can't
"wait until after SP1, for it to settle down".

Paul

On Mon, 05 Nov 2018 08:59:48 -0700, Ken Blake
wrote:

On Mon, 05 Nov 2018 09:49:06 +0000, Stephen Wolstenholme
wrote:

On Sun, 04 Nov 2018 09:54:36 -0700, Ken Blake
wrote:

On Sun, 04 Nov 2018 16:01:25 +0000, Terry Pinnell
wrote:

Trying to open Edge by any method fails. An empty window pops up only
briefly.

I've tried several suggested fixes so far in vain. Most attempts were
handicapped because I also had a freezing mouse problem. Now that's
fixed I'll repeat some 'fixes' methodically, but would appreciate any
suggestions please.




Here's my suggestion: stop trying to use Edge (the *worst* of all
available browsers, in my opinion) and switch to almost any other
browser. My personal choice is FireFox.

I agree with that. Edge is very poor. I've been using Chrome since
Google first produced it. I use bookmarks rather than shortcuts.



I'm in the great minority, I know, but as far as I'm concerned Edge is
the worst browser and Chrome is the second worst browser. It's only
slightly better than Edge.

I can't find anything wrong with Chrome. What should I know about it
that makes it a bad browser?

Steve

--
http://www.npsnn.com

On Tue, 06 Nov 2018 13:20:59 +0000, Stephen Wolstenholme
wrote:

On Mon, 05 Nov 2018 08:59:48 -0700, Ken Blake
wrote:

On Mon, 05 Nov 2018 09:49:06 +0000, Stephen Wolstenholme
wrote:

On Sun, 04 Nov 2018 09:54:36 -0700, Ken Blake
wrote:

On Sun, 04 Nov 2018 16:01:25 +0000, Terry Pinnell
wrote:

Trying to open Edge by any method fails. An empty window pops up only
briefly.

I've tried several suggested fixes so far in vain. Most attempts were
handicapped because I also had a freezing mouse problem. Now that's
fixed I'll repeat some 'fixes' methodically, but would appreciate any
suggestions please.




Here's my suggestion: stop trying to use Edge (the *worst* of all
available browsers, in my opinion) and switch to almost any other
browser. My personal choice is FireFox.

I agree with that. Edge is very poor. I've been using Chrome since
Google first produced it. I use bookmarks rather than shortcuts.



I'm in the great minority, I know, but as far as I'm concerned Edge is
the worst browser and Chrome is the second worst browser. It's only
slightly better than Edge.

I can't find anything wrong with Chrome. What should I know about it
that makes it a bad browser?


Sorry, it's been too long since I gave it a thorough try, and I can't
remember the details of what I didn't like about it.

But it really doesn't matter. You should ignore my preferences (and
everyone else's) and use what you like best.

Stephen Wolstenholme wrote:

Ken Blake wrote:

I'm in the great minority, I know, but as far as I'm concerned Edge is
the worst browser and Chrome is the second worst browser. It's only
slightly better than Edge.

I can't find anything wrong with Chrome. What should I know about it
that makes it a bad browser?

Not sure you'll get any details from Ken.

Perhaps Ken is arguing about privacy concerns. You don't need to have
Chrome log into a Google account. You don't need a Google account to
use Chrome. You can tweak Chrome or add extensions to undo some of the
security issues. You have to do the same with Firefox since Mozilla has
added support for features that you might want disabled. I have both
Google Chrome and Firefox. Both need to be locked down from their
install-time configs.

An advantage with Firefox is that you can go into about:config to make
tweaks that are not available in Chrome except by installing more
extensions. In Firefox, it's an option to focus on (move to) tabs after
clicking on a hyperlink. In Chrome, you have to install an extension.

However, some settings in Firefox are overly coarse. Disabling WebRTC
in Firefox kills all of it. The WebRTC Leak Prevent extension for
Chrome is more elegant. In Firefox with WebRTC disabled, I cannot use
the Google Voice site but it is usable in Chrome with the extension yet
testing at https://ipleak.net/ shows Chrome with the extension has
WebRTC blocked. With the extension, I can select different policies,
like blocking WebRTC only on the public interface, public and private,
or to force use of a proxy.

Firefox is still a little slower and less HTML5 compliant (plus Mozilla
has added their own "spin" or added features on some HTML5 elements that
are non-standard) than Chrome but I can more easily tweak Firefox.
Google keeps taking away handy tweaks in chrome://flags but some remain
that I want, like "Save page as MHTML" (enabled) and "Identity
consistency between browser and cookie jar" (disabled).

If Firefox Quantum were configured to similar to Chrome regarding the
maximum number of content processes allowed, Firefox would be an extreme
memory hog compared to Chrome.

Google came up with "Strict site isolation" (experimental at first, now
standard) long before Mozilla got around to mitigating Meltdown and
Spectre.

Mozilla had a defect with their Site Preferences feature that would
allow tracking of a particular Firefox instance due to retention of HSTS
supercookies across non-private sessions. The only fix is to configure
Firefox to purge all Site Preferences upon exit, always use private
sessions in Firefox, or keep deleting the SiteSecurityServiceState.txt
file after exiting Firefox. HSTS supercookies are saved between
non-private sessions while they are deleted between private session;
however, HSTS supercookies aren't deleted until you exit the private
browser session, so there is still possible tracking across tabs within
the same session. I just have Firefox purge everything, including Site
Preferences, upon its exit. Alas, the demo site for testing HSTS
supercookies (http://www.radicalresearch.co.uk/lab/hstssupercookies) no
longer exists. Testing of Google Chrome showed it wasn't retaining HSTS
supercookie data between sessions. You can see Chrome's HSTS
supercookie info at chrome://net-internals/#hsts. I queried on
google.com and it listed one, so I'm not sure how the demo page declares
HSTS supercookies cannot be used to track you. In Firefox, you cannot
see individual HSTS supercookie data as it is buried into the Site
Preferences database.

Firefox has an about:config setting to disable its captive portal
detection (which sends a success.txt test file to firefox.com). Google
added it in v63 about half a year later. Firefox sends traffic to an
unintended server (not to where the user pointed the web browser).
Google also sends traffic to gstatic.com or google.com. Both go out to
a test server to check if the client can reach it (not captive) or not
(captive). I haven't found how to disable captive portal detection in
Chrome. --disable-chrome-captive-portal-detector command-line switch is
only available when using a shortcut or command line, not when clicking
on a hyperlink, plus this switch was removed back in 2013 by a single
user request without discussion.

No matter which web browser you use, even those that claim to be more
secure, it's still up to you to know how to configure it to be MORE
secure depending on what functions you want to throttle when exposing
yourself in the Web.

On Tue, 6 Nov 2018 11:53:25 -0600, VanguardLH wrote:

Stephen Wolstenholme wrote:

Ken Blake wrote:

I'm in the great minority, I know, but as far as I'm concerned Edge is
the worst browser and Chrome is the second worst browser. It's only
slightly better than Edge.

I can't find anything wrong with Chrome. What should I know about it
that makes it a bad browser?

Not sure you'll get any details from Ken.

Perhaps Ken is arguing about privacy concerns.


No. My dislike of Chrome mostly had to do with its interface, but as I
said, I don't remember the details.


You don't need to have
Chrome log into a Google account. You don't need a Google account to
use Chrome. You can tweak Chrome or add extensions to undo some of the
security issues.


Yes, I know all of those things.

Ken Blake wrote:

VanguardLH wrote:

You don't need to have Chrome log into a Google account. You don't
need a Google account to use Chrome. You can tweak Chrome or add
extensions to undo some of the security issues. ...
snipped all the other comments

Yes, I know all of those things.

Oh (raised eyebrow with side glance), okay.

On Tue, 6 Nov 2018 19:29:30 -0600, VanguardLH wrote:

Ken Blake wrote:

VanguardLH wrote:

You don't need to have Chrome log into a Google account. You don't
need a Google account to use Chrome. You can tweak Chrome or add
extensions to undo some of the security issues. ...
snipped all the other comments

Yes, I know all of those things.

Oh (raised eyebrow with side glance), okay.


You don't believe me? That's fine. I don't care whether or not you do.