When you have no problems: The Microsoft Helpdesk calls you. Offers to take over your computer and fix all kinds of computer and security problems that you did not even know you had.
When you have severe problems with Microsoft services: There is no Helpdesk. You're on your own.
Good news is that this issue is getting some media attention. Yesterday it was featured on the primary Dutch ICT news website Tweakers.net. Sometimes media attention can fix what individual users or developers cannot.
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@hypernl: indeed, media coverage helped get Microsoft attention and also bring others to speak about this issue. Social media has a big power with this respect.
❤️
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you all for your feedback and your support in getting media attention through various social platforms.
After posting this, other developers in the security fields (like WireGuard) came forward to announce that they have the exact same issue. I understand why nobody talked publicly about this before and I'm glad that by going public I pushed others to do the same.
Positive aspect is that a Microsoft VP (Scott Hanselman) has announced on X that he will help address this issue affecting me and others. He also reached out to me and connected me with other Microsoft people to help address this issue.
I will let you know how things go.
👍
2
❤️
4
🎉
2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I just wanted to let you know that I have regained access to my Microsoft Partner Center account. Mr Scott Hanselman's intervention was key to getting this issue resolved and I am very grateful to him.
A big thank you as well to the community whose support helped trigger widespread media coverage of this issue affecting me and other security projects. It feels good to see the positive power of social media in making our voices heard.
Now I can finally prepare the long-overdue upcoming release. I will share timeline updates in the coming days.
🎉
6
😄
1
❤️
7
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thank you Mounir for all your work over the years!
My thoughts:
Really, a VP of a Fortune-500 company had to personally(!) intervene (and only after global widespread media coverage) in an account recovery process??? This shows how broken such automatic processes can be designed.
I am really reliefed, that you could manage this issue!!!
Congratulations on your persistance.
❤️
2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Cheers to the perseverance that the community and developers have shown against Microsoft! And thank you for the fact that every now and then there are still people with insight into the processes!
👍
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good news is that this issue is getting some media attention. Yesterday it was featured on the primary Dutch ICT news website Tweakers.net. Sometimes media attention can fix what individual users or developers cannot.
@hypernl: indeed, media coverage helped get Microsoft attention and also bring others to speak about this issue. Social media has a big power with this respect.
Thank you all for your feedback and your support in getting media attention through various social platforms.
After posting this, other developers in the security fields (like WireGuard) came forward to announce that they have the exact same issue. I understand why nobody talked publicly about this before and I'm glad that by going public I pushed others to do the same.
Positive aspect is that a Microsoft VP (Scott Hanselman) has announced on X that he will help address this issue affecting me and others. He also reached out to me and connected me with other Microsoft people to help address this issue.
I will let you know how things go.
@idrassi
Remember that the VeraCrypt community loves you and needs you. Thank you for everything you do
There's an old saying that the squeaky wheel gets the grease. Here's an example of some loud squeaking with high levels of readership...
https://www.neowin.net/news/microsoft-pulls-developer-accounts-of-wireguard-and-veracrypt/
It's great to see the support that the developer of this program receives!
Hello everyone,
I just wanted to let you know that I have regained access to my Microsoft Partner Center account. Mr Scott Hanselman's intervention was key to getting this issue resolved and I am very grateful to him.
A big thank you as well to the community whose support helped trigger widespread media coverage of this issue affecting me and other security projects. It feels good to see the positive power of social media in making our voices heard.
Now I can finally prepare the long-overdue upcoming release. I will share timeline updates in the coming days.
Thank you Mounir for all your work over the years!
My thoughts:
Really, a VP of a Fortune-500 company had to personally(!) intervene (and only after global widespread media coverage) in an account recovery process??? This shows how broken such automatic processes can be designed.
I am really reliefed, that you could manage this issue!!!
Congratulations on your persistance.
Awesome! Will there be also a new EFI bootloader signed for secure boot?
@davidxanatos: yes, there will be a new signed bootloader. there are pending fixes for bootloader. Target est 1.27 with new bootloader.
Cheers to the perseverance that the community and developers have shown against Microsoft! And thank you for the fact that every now and then there are still people with insight into the processes!
Good news about this strange story!
Hope that Wireguard team has a solution too.
This whole story confirms the reason why I left Windows for Linux. Microslop has no clue wtf they're doing.