I can no longer push my latest commit after the February 13, 2019 update.

Description

When I click the button to push origin, I get a fatal error that says "fault: unable to access 'repo name': schannel" next InitializeSecurityContext failed: Uknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.". I do not have any corporate proxy settings enabled and disabling my firewall and other antivirus protections didn't solve this issue, which is what others with this issue suggested.

Version

• GitHub Desktop: 1.6.2

• Operating system: Windows 8.1 Pro

Steps to Reproduce

Step 1: Click "push origin".

Expected Behavior

I expected the push to work successfully.

Actual Behavior

Can't push changes.

Additional Information

Logs

2019-02-15T16:20:49.516Z - error: [ui] `git -c credential.helper= fetch --progress --prune origin` exited with an unexpected code: 128.

fatal: unable to access ‘Repo name’: schannel: next InitializeSecurityContext failed: Unknown error (0x80092013) - The revocation function was unable to check revocation because the revocation server was offline.

[shiftkey]

@rajzerm thanks for filling that out - I can understand more about what’s happening.

This feels like #3326, but I have a simpler workaround for you to try.

Git for Windows has an escape hatch to bypass these certificate revocation checks (since v2.19.0).

Try setting this global config value:

$ git config --global http.schannelCheckRevoke false

This should address the issue without needing to go and configure your own certificate bundle.

[shiftkey]

@rajzerm I’m glad you were able to resolve this, and thanks for confirming the new workaround works for you.

I’m going to leave this open and update our known issues doc to explain this new flag and recommend this workaround.