Another day, another bug found in Windows 10

Aug 7, 2015 12:31 GMT  ·  By

“Windows 10 is never done.” That's what Windows chief Terry Myerson said ahead of the July 29 launch, explaining that Microsoft switched to Windows as a Service and would continuously improve Windows 10 to make sure that everyone would be running the latest version of the operating system.

Criticism reaching the web in the last few days accuses the company of launching an unfinished product, pointing to the number of errors experienced by users as living proof.

Such an error is 0x80070032, which, according to a number of complains posted online, shows up when trying to synchronize the sent folder in the Mail app.

“Since July 30, I have Windows 10 installed. Not completely happy with it. Anyway, thre is this issue with the syncing of a folder in the new Windows 10 Mail in my account of outlook.com. I was able to sync the Inbox but for (an) unknown reason(s), The Sent Items folder will not sync. I tried now every day without any success,” one user said.

Error code 0x80070032

In most of the cases, the error that users are getting reads, “Something went wrong. We can't sync right now. But you may find more information about this error code at www.windowsphone.com. Error code: 0x80070032.”

Microsoft hasn't yet replied to this long Community forums discussion, but it appears that there are several other Mail errors encountered when trying to access the inbox.

Below is another message posted by one of the users attempting to synchronize the inbox:

“I get another cryptic message that ‘Something went wrong...’ and then ‘We can't connect to blu404-m.hotmail.com right now. Make sure you have a connection, and then try again. Error code: 0x80072ee2.’ I have a well working connection! I wonder why the sync process worked for the Inbox but not for the Sent Items, Deleted Items folders. The account is set as an IMAP. I had to go back to use Windows Live Mail 2012 which works fine.”

We've contacted Microsoft for more information on this error and a possible workaround, but we're yet to receive a reply, so we'll let you as soon as we figure out a way to fix the problem.