Sorry guys for the late response. I had a busy day yesterday!

@Ai I'm not sure why you haven't got access to the update yet, but it should be available. For Windows, there is definitely no rollout feature, so when it's published, that's it. It goes out all at once to all our customers. Now that doesn't mean it actually gets to everyone's computer immediately, of course, but there's nothing we can do to speed up that process. The only thing I can think is for some reason it's not yet propagated through all of the Microsoft Store's servers, but that still seems like a strange problem. It's been about a week now, so you should have it on your PCs. I would have thought everyone would have it within no more than a day of its release. If you do figure out what's happening, please do let me know.

@Jon I'll talk to our developer about this, but for what we're doing here, storing the EAK in Windows Web Credentials is a standard. It's encrypted data that needs to persist on the computer. Since Microsoft made it a global object, I know there's a reason for that, and I don't believe it provides any security risk for mSecure. You are correct that we could mention the EAK is stored in Windows Web Credentials and will be available on different profiles. However, I still don't know how that is seen as a liability. Are you thinking there's going to be a way for a hacker to create a new profile on your computer without your knowledge to steal your EAK?

I am all for making a change in how we're doing things here, but I do need to know why the change should be made. There are a couple of reasons we have not mentioned what we're talking about here. First, and most important, it should not be just any profile that can access the Web Credentials on your computer. To my knowledge, only Administrator accounts have access to them. So if you were to simply set up a profile that did not have admin access, that profile should not have access to your EAK. When you set up the profile on your computer Ken, did you set it up as an Admin profile?

Second, in order for this to be a problem, a hacker would have to steal your computer in order to have access to the EAK. In that case, you should always be changing first your mSecure password and then your other account passwords right away. And if you do that, it wouldn't matter that the EAK is anywhere on your computer. Also, if a hacker stole your computer, it wouldn't matter that the EAK could be accessed on other profiles. They would need to get Admin access, but that might not be difficult for a good hacker. In that case, they would simply be into your account and get whatever they want. I specifically mention a hacker in this example, because that would be the only person who would ever try to brute force attack the EAK to get access to your mSecure account. If it was a spouse or a child or friend, unless you know them to be hackers, they would never be able to do anything with that data.

Again, we are definitely open to us making changes here, so I'm really hoping what I'm saying doesn't come across as defensive. Please do give me your feedback, and you to @Ai if you would like, and we'll keep the discussion going as long as needed.

@Ai Ok, well, I was able to find your email address in one of the beta lists, so maybe that's causing the problem. It's not supposed to, because you're supposed to be served the the newest build you have access to. So since you have downloaded the production version onto your devices, even though you were on a beta list, the beta is an older version that what's in the store. However, I did remove it, so let's see it that fixes the problem.

Go ahead and stop the Store app and restart it. Then click Library and then Get Updates. Did 6.1 become available?

@Ai That's great it took care of the problem, and I'm sorry I didn't realize what was happening before you mentioned it! It just never occurred to me that you wouldn't get the newest version of the app. I'll have to keep that in mind if/when I run into this again.

With regards to the password history, are you saying that you just don't see the password history on Windows? If so, I think this might be due to that information not syncing over to Windows. Does it sync right on all your other devices?

@Mike I just found you in a beta list as well. I removed your email address, so maybe that will fix the issue for you to. Do you see mSecure in the Store app after closing and reopening, then clicking the Library button in the bottom left, and the clicking Get Updates?

@Noella Are you saying you're not seeing mSecure in the Microsoft Store or are you talking about the Apple App Stores? I just responded to you in another thread about how the rollout works for Apple's App Stores. However, I didn't think in that thread that you could have been talking about the Windows version of the app.