I want to share an update following my absence over the past few months.
I have encountered some challenges but the most serious one is that Microsoft terminated the account I have used for years to sign Windows drivers and the bootloader. You can see below a screenshot of the message shown when I tried to sign in.
Microsoft did not send me any emails or prior warnings. I have received no explanation for the termination and their message indicates that no appeal is possible.
I have tried to contact Microsoft through various channels but I have only received automated replies and bots. I was unable to reach a human.
This termination impacts my work beyond VeraCrypt and has consequences for my daily job.
Currently I'm out of options.
Regarding VeraCrypt, I cannot publish Windows updates. Linux and macOS updates can still be done but Windows is the platform used by the majority of users and so the inability to deliver Windows releases is a major blow to the project.
I'm open to proposals and help.
π
4
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Some practical questions about the most current Windows release, until this situation can be resolved:
The current version 1.26.24 is signed with the 2011 CA, which is soon to expire. This will certainly affect secureboot.... but how will this affect mounting non-system volumes (partitions and/or file containers) as a user? Will one have to disable secureboot just to install VeraCrypt, even if not using system encryption? And how will this affect portable use?
The same question applies to unsigned versions people may choose to build for themselves for Windows.
π
3
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@martymacgyver: for non-system volumes, there is no issue since driver will continue to work. For system encryption, inability to publish a new signed bootloader will definitely cause issues once the 2011 EFI CA is revoked later this year.
I prefer not to think about this possibility since there are positive signs that the issue will be resolved.
Let's wait and see.
π
3
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for that detail - it's useful information regardless. Given the widespread coverage of this situation I'm very hopeful that this will be resolved quickly!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Iβm so sorry to hear about this. I would try contacting Microsoft using the link below. There is a link to βHelp with the Microsoft account recovery formβ on this page:
There is also a link to βI need to talk to a customer support agentβ on that page. Apologies if you have already tried these links.
Alex Rβs kind suggestion of posting to Reddit and Twitter (now X) are great suggestions too since this will likely get you re-directed to the right people.
If your account has been disabled for more than 30 days it could be unrecoverable. You may need to set up a new account and start the verification process all over again to have your new account enabled for driver signing purposes.
I hope this is somewhat helpful. Thanks.
Last edit: AJ B 6 days ago
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry that you had already tried those suggestions. Itβs fabulous that you are receiving the right support now.
The entire community welcomes you back. Please do let us know if you encounter any other challenges we can you help with. I agree with @Xiu, the VeraCrypt community loves you and needs you.
Thank you so much!
π
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
In view of this situation, I recommend adding a signature-independent program that provides archive-like creation and extraction functions (without support for real-time modification), so as to cope with highly targeted scenarios.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@fzxx: We already have similar mechanism using GPG signatures. The issue here is that Microsoft holds the keys for SecureBoot on all the worlds PCs in addition to Windows driver signing keys so without their approval you are basically out of business!
π
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
This is a sad turn of events, Mounir! This may seem a bit out in left field (to use an American idiom), but is it possible that some seemingly minor aspect of your recent relocation to Japan is at the root of this inexplicable account revocation?
Grasping at straws is a hobby of mine :)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@garymarks: Thank you for the feedback. Judging by the fact that other projects like WireGuard are affected, I don't think my move to Japan has anything to do with it. There seem to be an internal Microsoft policy that triggered this issue at large scale and there lack of communication and feedback made things worse.
positive signs are coming...crossing fingers that it will be solved soon.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm really sorry to hear this bad news. Someone probably reported the software, claiming it could be used for illegal activities, which led to the account being deleted. Unfortunately, the general trend is increasingly toward controlling and monitoring what people do, and there is less and less respect for privacy.
Is there no way to get around this limitation, even temporarily? Perhaps by restricting the software, for now, to non-system partitions and volumes?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@phoenix-rising: there is no real secure solutions or workaround if Microsoft doesn't sign the driver or bootloader. Other solutions degrade Windows security and I will never recommend them: in such cases, it is better to move to another operating system like Linux.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I would try sending an email to Microsoft CEO, Satya Nadella at:
satyan@microsoft.com
Use brief details from your first post in this thread along with the error message screenshot.
Possible email shown below.
Subject Line: Reinstate Partner Center Program Account for my Software Developer Business
Dear Satya Nadella,
I need someone from your staff's to help me get my Partner Center program account reinstated for my Windows developer business.
I attempted to login to my Partner Center account and I received the following error message.
insert your screenshot of error here
I did not receive from Microsoft any email notices or prior warnings that there is an issue with my Partner Center account and I have contacted support for assistance without results.
This issue impacts my business to provide third-party Windows software.
Kind Regards,
Mounir Idrassi insert your business(es) name(s) insert your business email insert your business phone number and any alternate phone numbers insert your business address
Time zone : JST (UTC+9)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
At the end, social media postings and interview with journalists helped trigger a response from Microsoft especially that other projects turned out to be affected.
Microsoft VP Scott Hanselman reached out to help few hours ago. Hopefully it will be sorted out soon.
π
1
π
1
π
3
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First, I doubt (hope not!) the account is actually deleted, it's most likely just disabled/turned off. Your accounr is just in the recycle bin... :)
I would email people in the crypto community/other devs who would know someone at MS - bruce schneir, chris titus, niels ferguson; or are someone at MS - karen easterbrook, nathan ide.
I would also contact media - tom's hardware, ars techica, wired, the intercept, EFF. there are a bunch of reddit subs that would apply - both in the privacy and crypto areas. also the guys from the all-in podcast and elon musk.
I would also contact the offices of the following US congressmen and ask for help: Reps: Tom Massie and Senators: Rand Paul, Ron Wyden. Even though you're not a US citizen, there is a compelling privacy interest for US citizens who are the bulk (guessing) of the users of this software.
π
2
Last edit: Preguntar Jeeves 2026-04-06
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@geeivegotmail: Thank you for the feedback. Definitely media coverage helped to get Microsoft publicly communicate about this. Big thanks to the community for this.
π
2
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hey Mounir, do you have an email I can share with Microsoft? (you can email me at rafael@withinwindows.com) I can help route this to the right folks internally.
π
1
β€οΈ
4
Last edit: Rafael Rivera 6 days ago
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@withinrafael: Thank you for your proposal. Few hours ago I was contacted by a Microsoft VP (Scott Hanselman) following the media coverage. He connected me with the right people from Microsoft and hopefully things will be sorted out soon.
I will share updates.
π
1
β€οΈ
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Mounir. Just so you know, I ran into the exact same issue you mention when I tried to update my developer legal info for Secure Boot signing (you can see the full screenshot I got on my side, with the same error message in https://github.com/pbatard/rufus/issues/2918#issuecomment-3893620279).
I was able to get it sorted after contacting Microsoft support through the Partner Center and, from what I gather, the "There are no appeals available" is just boilerplate text that pertains to a separate part of the process that isn't directly tied with the formal business validation.
In my case (as far as I can tell), the issue was that I my domain name was from a .ie registrar and not a .com/.org for which Microsoft could automatically validate the WHOIS data. It is my understanding that the error message we both get is is what Microsoft defaults to when their automated WHOIS validation fails.
I have to say that, once I got hold of them, the Microsoft support people were quite helpful and managed to get my business validation sorted, once I provided them with the relevant data from the registrar (mostly my last domain registration invoices).
Hopefully, your issue is similar to mine, and will be resolved quickly once you get hold of someone at Microsoft.
π
3
β€οΈ
1
Last edit: Pete Batard 6 days ago
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@pbatard: thank you for sharing your experience. In my case, I was never able to get in touch with a human. I tried every possible contact form and link and every time it was automatic or AI feedback.
Seeing others affected like clearly show that there is a a communication issue on the side of Microsoft. Deploying automated systems that take such radical decisions should come with clear feedback and messaging to affected people so that adequate actions could be taken.
π
1
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi everyone,
I want to share an update following my absence over the past few months.
I have encountered some challenges but the most serious one is that Microsoft terminated the account I have used for years to sign Windows drivers and the bootloader. You can see below a screenshot of the message shown when I tried to sign in.
Microsoft did not send me any emails or prior warnings. I have received no explanation for the termination and their message indicates that no appeal is possible.
I have tried to contact Microsoft through various channels but I have only received automated replies and bots. I was unable to reach a human.
This termination impacts my work beyond VeraCrypt and has consequences for my daily job.
Currently I'm out of options.
Regarding VeraCrypt, I cannot publish Windows updates. Linux and macOS updates can still be done but Windows is the platform used by the majority of users and so the inability to deliver Windows releases is a major blow to the project.
I'm open to proposals and help.
Some practical questions about the most current Windows release, until this situation can be resolved:
The current version 1.26.24 is signed with the 2011 CA, which is soon to expire. This will certainly affect secureboot.... but how will this affect mounting non-system volumes (partitions and/or file containers) as a user? Will one have to disable secureboot just to install VeraCrypt, even if not using system encryption? And how will this affect portable use?
The same question applies to unsigned versions people may choose to build for themselves for Windows.
@martymacgyver: for non-system volumes, there is no issue since driver will continue to work. For system encryption, inability to publish a new signed bootloader will definitely cause issues once the 2011 EFI CA is revoked later this year.
I prefer not to think about this possibility since there are positive signs that the issue will be resolved.
Let's wait and see.
Thanks for that detail - it's useful information regardless. Given the widespread coverage of this situation I'm very hopeful that this will be resolved quickly!
Hi Mounir,
Iβm so sorry to hear about this. I would try contacting Microsoft using the link below. There is a link to βHelp with the Microsoft account recovery formβ on this page:
https://support.microsoft.com/en-us/account-billing/get-help-with-your-microsoft-account-ace6f3b3-e2d3-aeb1-6b96-d2e9e7e52133
There is also a link to βI need to talk to a customer support agentβ on that page. Apologies if you have already tried these links.
Alex Rβs kind suggestion of posting to Reddit and Twitter (now X) are great suggestions too since this will likely get you re-directed to the right people.
If your account has been disabled for more than 30 days it could be unrecoverable. You may need to set up a new account and start the verification process all over again to have your new account enabled for driver signing purposes.
I hope this is somewhat helpful. Thanks.
Last edit: AJ B 6 days ago
@ajb87351: Thank you for the feedback. I already tried all the links.
Clearly media coverage has more power and the fact that other projects are affected helped gain more traction.
Everybody was silent because of the power Microsoft holds. I'm glad my first move triggered this collective reactions to make our voices heard.
Hi Mounir,
Sorry that you had already tried those suggestions. Itβs fabulous that you are receiving the right support now.
The entire community welcomes you back. Please do let us know if you encounter any other challenges we can you help with. I agree with @Xiu, the VeraCrypt community loves you and needs you.
Thank you so much!
Would you be OK if I posted this to socials, such as Microsoft's reddit or twitter accounts? Might get some traction.
yes, no problem. I don't have much social presence so this can be helpful. Thanks.
In view of this situation, I recommend adding a signature-independent program that provides archive-like creation and extraction functions (without support for real-time modification), so as to cope with highly targeted scenarios.
@fzxx: We already have similar mechanism using GPG signatures. The issue here is that Microsoft holds the keys for SecureBoot on all the worlds PCs in addition to Windows driver signing keys so without their approval you are basically out of business!
This is a sad turn of events, Mounir! This may seem a bit out in left field (to use an American idiom), but is it possible that some seemingly minor aspect of your recent relocation to Japan is at the root of this inexplicable account revocation?
Grasping at straws is a hobby of mine :)
@garymarks: Thank you for the feedback. Judging by the fact that other projects like WireGuard are affected, I don't think my move to Japan has anything to do with it. There seem to be an internal Microsoft policy that triggered this issue at large scale and there lack of communication and feedback made things worse.
positive signs are coming...crossing fingers that it will be solved soon.
I'm really sorry to hear this bad news. Someone probably reported the software, claiming it could be used for illegal activities, which led to the account being deleted. Unfortunately, the general trend is increasingly toward controlling and monitoring what people do, and there is less and less respect for privacy.
Is there no way to get around this limitation, even temporarily? Perhaps by restricting the software, for now, to non-system partitions and volumes?
@phoenix-rising: there is no real secure solutions or workaround if Microsoft doesn't sign the driver or bootloader. Other solutions degrade Windows security and I will never recommend them: in such cases, it is better to move to another operating system like Linux.
@idrassi
I would try sending an email to Microsoft CEO, Satya Nadella at:
satyan@microsoft.com
Use brief details from your first post in this thread along with the error message screenshot.
Possible email shown below.
Subject Line: Reinstate Partner Center Program Account for my Software Developer Business
Dear Satya Nadella,
I need someone from your staff's to help me get my Partner Center program account reinstated for my Windows developer business.
I attempted to login to my Partner Center account and I received the following error message.
insert your screenshot of error hereI did not receive from Microsoft any email notices or prior warnings that there is an issue with my Partner Center account and I have contacted support for assistance without results.
This issue impacts my business to provide third-party Windows software.
Kind Regards,
Mounir Idrassi
insert your business(es) name(s)insert your business emailinsert your business phone number and any alternate phone numbersinsert your business addressTime zone :
JST (UTC+9)@enigma2illusion: Thank you for the proposal.
At the end, social media postings and interview with journalists helped trigger a response from Microsoft especially that other projects turned out to be affected.
Microsoft VP Scott Hanselman reached out to help few hours ago. Hopefully it will be sorted out soon.
Good to hear, does that mean RTM 1.26.27 is coming soon?
Last edit: ara ara 5 days ago
First, I doubt (hope not!) the account is actually deleted, it's most likely just disabled/turned off. Your accounr is just in the recycle bin... :)
I would email people in the crypto community/other devs who would know someone at MS - bruce schneir, chris titus, niels ferguson; or are someone at MS - karen easterbrook, nathan ide.
I would also contact media - tom's hardware, ars techica, wired, the intercept, EFF. there are a bunch of reddit subs that would apply - both in the privacy and crypto areas. also the guys from the all-in podcast and elon musk.
I would also contact the offices of the following US congressmen and ask for help: Reps: Tom Massie and Senators: Rand Paul, Ron Wyden. Even though you're not a US citizen, there is a compelling privacy interest for US citizens who are the bulk (guessing) of the users of this software.
Last edit: Preguntar Jeeves 2026-04-06
@geeivegotmail: Thank you for the feedback. Definitely media coverage helped to get Microsoft publicly communicate about this. Big thanks to the community for this.
yeay! Scott's a good guy. Totally forgot about him still working for MS.
Hey Mounir, do you have an email I can share with Microsoft? (you can email me at rafael@withinwindows.com) I can help route this to the right folks internally.
Last edit: Rafael Rivera 6 days ago
@withinrafael: Thank you for your proposal. Few hours ago I was contacted by a Microsoft VP (Scott Hanselman) following the media coverage. He connected me with the right people from Microsoft and hopefully things will be sorted out soon.
I will share updates.
Hi Mounir. Just so you know, I ran into the exact same issue you mention when I tried to update my developer legal info for Secure Boot signing (you can see the full screenshot I got on my side, with the same error message in https://github.com/pbatard/rufus/issues/2918#issuecomment-3893620279).
I was able to get it sorted after contacting Microsoft support through the Partner Center and, from what I gather, the "There are no appeals available" is just boilerplate text that pertains to a separate part of the process that isn't directly tied with the formal business validation.
In my case (as far as I can tell), the issue was that I my domain name was from a .ie registrar and not a .com/.org for which Microsoft could automatically validate the WHOIS data. It is my understanding that the error message we both get is is what Microsoft defaults to when their automated WHOIS validation fails.
I have to say that, once I got hold of them, the Microsoft support people were quite helpful and managed to get my business validation sorted, once I provided them with the relevant data from the registrar (mostly my last domain registration invoices).
Hopefully, your issue is similar to mine, and will be resolved quickly once you get hold of someone at Microsoft.
Last edit: Pete Batard 6 days ago
@pbatard: thank you for sharing your experience. In my case, I was never able to get in touch with a human. I tried every possible contact form and link and every time it was automatic or AI feedback.
Seeing others affected like clearly show that there is a a communication issue on the side of Microsoft. Deploying automated systems that take such radical decisions should come with clear feedback and messaging to affected people so that adequate actions could be taken.