#533 Can not automaticly block TecentQQ access to camera, even if I set avp block all program access camera.

  • Information provided

    I reboot soemtimes

    result is the same.

    cannot figure out waht made my last installation malfunction.......

    System Settings

    Operating system: Win 10, x64

    System: whatever

    Product: KTS

    Product Version: 2019 MR0

    Language: en-US

    Product Logs: https://cloud.qainfo.ru/s/gEhDffeO3wyqPt6

  • update to patch C again

    It is miracle that I cannot reproduce again.

    webcam protection work fine on uwp camera app and QQ.

    I do not know why, but the problem is no more reproduced.......

  • This post is deleted!
  • This post is deleted!
  • This post is deleted!
  • , last edited by Jowi
    This post is deleted!
  • @stepan-korchagin

    I did a quick test

    OS windows10 RS4 17134.286 x64

    all test are performed in above OS.

    KIS19.0.0.1088 (a) en-us

    uwp camera program: fail to block access to camera using any means.( No green window in screen, also No use if check 'block all app use camera')

    QQ: block and show green window both work fine. no problem


    uwp camera program: same above, fail to block. fail to capture the activaty using camera.

    QQ: block and show green window both work fine. no problem.

  • @stepan-korchagin

    May take quite a long time.

    I believe I should have given you the report next day...

  • @xzz123can it be result of QQ update? Can you check it for patch B or A now?

  • , last edited by xzz123


    No, can not reproduce in 2020

    but in previews patch for 2018, there is no problem. Also no problem in 2019 patch A.

    One day, I remember, after update of patch B for 2019, webcam protection became useless for all program, not just QQ. 

    After patchC fix the issue( this was mentioned in release note of patchC), only blocking QQ use camera become a problem.

    Webcam protection useless for QQ is not a new bug, I reprot such problem to support approximately a year ago.

  • Is that issue also actual for 2020?

    Looks like it is not patch issue, because it also present for 2018

  • It is highly likely that patch K for 2018 product also share the same problem.

Looks like your connection to Beta Testing was lost, please wait while we try to reconnect.