# Authorization result unknown on upgrade **URL:** \ **Category:** Windows\ **Created:** [February 13, 2024, 2:40pm UTC](https://devforum.zoom.us/t/authorization-result-unknown-on-upgrade/103766 "2024-02-13T14:40:35Z")\ **Posts on this page:** 17\ **Page:** 1
**Author:** ![ZMUCW](https://avatars.discourse-cdn.com/v4/letter/z/b5ac83/32.png) [@ZMUCW](https://devforum.zoom.us/u/ZMUCW)\ **Post date:** [February 13, 2024, 2:40pm UTC](https://devforum.zoom.us/t/authorization-result-unknown-on-upgrade/103766/1 "2024-02-13T14:40:35Z")
**Description** After upgrading to Windows SDK version 5.17.6.31095, we are sporadically getting an AuthResult.Unknown when attempting to authorize the SDK immediately after the upgrade. - OS: Windows 11 We have ZDK logs that can be shared ---
**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\ **Post date:** [February 14, 2024, 4:43am UTC](https://devforum.zoom.us/t/authorization-result-unknown-on-upgrade/103766/2 "2024-02-14T04:43:30Z")
@ZMUCW ,which version of SDK did you previously upgraded from? In Zoom Meeting SDK 5.14.10 onwards, the SDK authentication requires you to sign your auth token using your SDK Key and SDK Secret ---
**Author:** ![ZMUCW](https://avatars.discourse-cdn.com/v4/letter/z/b5ac83/32.png) [@ZMUCW](https://devforum.zoom.us/u/ZMUCW)\ **Post date:** [February 15, 2024, 6:05pm UTC](https://devforum.zoom.us/t/authorization-result-unknown-on-upgrade/103766/3 "2024-02-15T18:05:01Z")
We are using the Key and Secret. We upgraded from 5.15.2.18146. Can I submit the SDK logs? ---
**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\ **Post date:** [February 16, 2024, 4:56am UTC](https://devforum.zoom.us/t/authorization-result-unknown-on-upgrade/103766/4 "2024-02-16T04:56:53Z")
@ZMUCW , could you try to capture the log where this happen and provide a download link for this? ---
**Author:** ![ZMUCW](https://avatars.discourse-cdn.com/v4/letter/z/b5ac83/32.png) [@ZMUCW](https://devforum.zoom.us/u/ZMUCW)\ **Post date:** [February 16, 2024, 1:28pm UTC](https://devforum.zoom.us/t/authorization-result-unknown-on-upgrade/103766/5 "2024-02-16T13:28:49Z")
[Sdk Dumps](https://drive.google.com/drive/folders/1PJ-jhVQ6znek98VNnonZz4AJpIKlMw90?usp=drive_link) should contain dumps where this is occuring ---
**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\ **Post date:** [February 21, 2024, 4:47am UTC](https://devforum.zoom.us/t/authorization-result-unknown-on-upgrade/103766/6 "2024-02-21T04:47:18Z")
@ZMUCW 1. Does this keeps happening everytime, or is this intermittent? 2. Are there additional error code from the SDK? 3. Are you also using a proxy for the SDK auth? ---
**Author:** ![ZMUCW](https://avatars.discourse-cdn.com/v4/letter/z/b5ac83/32.png) [@ZMUCW](https://devforum.zoom.us/u/ZMUCW)\ **Post date:** [February 21, 2024, 2:20pm UTC](https://devforum.zoom.us/t/authorization-result-unknown-on-upgrade/103766/7 "2024-02-21T14:20:20Z")
1. Does this keeps happening everytime, or is this intermittent? It is intermittent. 2. Are there additional error code from the SDK? No other error codes 3. Are you also using a proxy for the SDK auth? Not sure, we use the c# wrapper. ---
**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\ **Post date:** [February 23, 2024, 4:46am UTC](https://devforum.zoom.us/t/authorization-result-unknown-on-upgrade/103766/8 "2024-02-23T04:46:50Z")
@ZMUCW , I don’t see much from the logs from a brief investigation. I do see in the logs that there seems to be calls and malformed URL for authentication . Are you behind a firewall or proxy by the way? I’m wondering if outgoing traffic is being filtered or blocked. ---
**Author:** ![ZMUCW](https://avatars.discourse-cdn.com/v4/letter/z/b5ac83/32.png) [@ZMUCW](https://devforum.zoom.us/u/ZMUCW)\ **Post date:** [February 28, 2024, 4:27pm UTC](https://devforum.zoom.us/t/authorization-result-unknown-on-upgrade/103766/9 "2024-02-28T16:27:03Z")
This only seems to occur on Windows 11 systems. Not sure if there a default firewall that could be causing it. ---
**Author:** ![ZMUCW](https://avatars.discourse-cdn.com/v4/letter/z/b5ac83/32.png) [@ZMUCW](https://devforum.zoom.us/u/ZMUCW)\ **Post date:** [February 28, 2024, 5:32pm UTC](https://devforum.zoom.us/t/authorization-result-unknown-on-upgrade/103766/10 "2024-02-28T17:32:30Z")
Another data point. It seams to happen if our application is killed rather than being properly shutdown. ---
**Author:** ![ZMUCW](https://avatars.discourse-cdn.com/v4/letter/z/b5ac83/32.png) [@ZMUCW](https://devforum.zoom.us/u/ZMUCW)\ **Post date:** [March 1, 2024, 4:41pm UTC](https://devforum.zoom.us/t/authorization-result-unknown-on-upgrade/103766/11 "2024-03-01T16:41:08Z")
One other point, we attempted with 5.16.6.24762 of the sdk and have the same issue. ---
**Author:** ![ZMUCW](https://avatars.discourse-cdn.com/v4/letter/z/b5ac83/32.png) [@ZMUCW](https://devforum.zoom.us/u/ZMUCW)\ **Post date:** [March 5, 2024, 6:24pm UTC](https://devforum.zoom.us/t/authorization-result-unknown-on-upgrade/103766/12 "2024-03-05T18:24:50Z")
On a fresh Windows 11 VM with Windows Defender Firewall entirely disabled the issue still appears sporadically. I have added a new log to the share folder. ---
**Author:** ![ZMUCW](https://avatars.discourse-cdn.com/v4/letter/z/b5ac83/32.png) [@ZMUCW](https://devforum.zoom.us/u/ZMUCW)\ **Post date:** [March 12, 2024, 4:07pm UTC](https://devforum.zoom.us/t/authorization-result-unknown-on-upgrade/103766/13 "2024-03-12T16:07:45Z")
With 5.15.2.18146 on the same PCs there is no issue. Did something change between 5.15 and 5.16 that could have caused this? We need to upgrade to at least 5.15.5 by May 4 base on your SDK minimum version policy. However, we were planning on upgrading to as high a version as possibly to avoid the needing to redo the work for the August 4 enforcement which is still TBA. We can’t release 5.16 and higher to our customers until we figure out a resolution to this issue. ---
**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\ **Post date:** [March 14, 2024, 3:51am UTC](https://devforum.zoom.us/t/authorization-result-unknown-on-upgrade/103766/14 "2024-03-14T03:51:46Z")
I’ll pm you for this @ZMUCW ---
**Author:** ![cai.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/cai.zoom/32/29704_2.png) [@cai.zoom](https://devforum.zoom.us/u/cai.zoom)\ **Post date:** [April 4, 2024, 1:18pm UTC](https://devforum.zoom.us/t/authorization-result-unknown-on-upgrade/103766/15 "2024-04-04T13:18:26Z")
hi @chunsiong.zoom @ZMUCW What was the resolution here ? I am also experiencing the same issue. Is this due to windows 11 OS ? ---
**Author:** ![chunsiong.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/chunsiong.zoom/32/35488_2.png) [@chunsiong.zoom](https://devforum.zoom.us/u/chunsiong.zoom)\ **Post date:** [April 4, 2024, 2:03pm UTC](https://devforum.zoom.us/t/authorization-result-unknown-on-upgrade/103766/16 "2024-04-04T14:03:38Z")
@cai.zoom this was suspected to be due to some firewall filtering. We did not managed to find the root cause as there was no captured SDK log when this happened. ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\ **Post date:** [May 5, 2024, 12:03am UTC](https://devforum.zoom.us/t/authorization-result-unknown-on-upgrade/103766/17 "2024-05-05T00:03:54Z")
Closed on May 5, 2024, 12:03am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.