An internal error occurred while enumerating backup sets
Hi buddies.
Maybe you know how to solve this problem I'm getting. I have a backup policy in my server, that makes a full image. I'm able to restore that image (using the windows cd) if it's located in an USB HDD, but if I try to load the image trough a network share, the quoted error message appears...
Any idea? I've tried in different servers, locations, sharing permisions...
Thx!
Hi Daniel,
Please copy the contents in the USB hard disk to a folder on a remote computer and the share the folder to test this issue again. To perform the restore from a network location, please refer to the following blog article:
Windows Server Backup 2008 Restore from Network Location
Laura Zhang - MSFT
- Marked as answer by DanielSVargas Tuesday, September 27, 2011 12:14 PM
Hi,
Please check whether you backup to the network share directly or copy the backup content from the USB HDD to the network share?
If you copy backup contents form USB HDD to the network share, in the course of copy, it may be something gets corrupted.
If so , I suggest you backup content to network share directly instead of copying from the USB HDD to the network share.
BTW, you can refer to the following post to check the backup on the network with cmdline.
Windows Server Backup Restore "Failed to Enumerate backup sets"
Best Regards,
Jeff Ren
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Please remember to click "Mark as Answer" on the post that helps you, and to click "Unmark as Answer" if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Hi Jeff,
I haven't had time to read your link, but my scenario is pretty simple. I have an external USB HDD, with the image in the root.
If I plug the HDD and I boot from the Windows DVD, I can restore the image perfectly.
If I plug the HDD in other computer, and share it, I get that error when retrieving the backup from the network...
So the backup integrity is OK...
I'll try to read the link ASAP.
Thanks ;)
Hi Daniel,
Please copy the contents in the USB hard disk to a folder on a remote computer and the share the folder to test this issue again. To perform the restore from a network location, please refer to the following blog article:
Windows Server Backup 2008 Restore from Network Location
Laura Zhang - MSFT
- Marked as answer by DanielSVargas Tuesday, September 27, 2011 12:14 PM
Now it worked copying the backup to a local folder and sharing it, and it also worked sharing the backup form the external hdd...
I don't know what I was missing, but the point is that is working.
Thanks!
I get this error as well. You know, it shouldn't be this hard.
I have a 2TB external hard drive. I made a backup, replaced the failing hard drive, then booted off a system recovery disk.
The external HDD doesn't show up as a location.
Fine, so I move it to another PC, and setup a share to the root. I get the error "An internal error occurred while enumerating backup sets"
I check the event log on the source PC, and it shows a sucesful login. Yet "An internal error occurred while enumerating backup sets"
So I setup a share to "WindowsImageBackup". Now, I don't get the error, but it finds NO backup sets, despite the fact 2-3 are in there.
I even tried browsing to each folder, thinking there was a permissions problem, but that all worked.
I did find this in the event log:
An IPsec main mode negotiation failed.
Local Endpoint:
Local Principal Name: -
Network Address: 192.168.0.198
Keying Module Port: 500
Remote Endpoint:
Principal Name: -
Network Address: 192.168.0.196
Keying Module Port: 500
Additional Information:
Keying Module Name: AuthIP
Authentication Method: Unknown authentication
Role: Responder
Impersonation State: Not enabled
Main Mode Filter ID: 0
Failure Information:
Failure Point: Local computer
Failure Reason: No policy configured
State: No state
Initiator Cookie: 12c88e049c741881
Responder Cookie: ed9a52c5f4b8db35
Any ideas?
== John ==
== John ==
Hi All,
I had the same issue and found that it was because I had multiple backups of DIFFERENT operating systems in the WindowsImageBackup folder. [\\server\backups\WindowsImageBackup] I was trying to restore a Windows 7 image from the share which contained Windows 8 and Windows 2012 images also.
I created a new share on the server, created the WindowsImageBackup folder in the share and copied the required Windows 7 backup folder in.
With this setup the restore completed without issue.
I tried a Windows 8 and Windows 2012 restore from the folder containing multiple OS backups and they enumerate and restore fine. So it appears to be that the enumeration fails if there are later OS version backups in the folder. Well for me at least.
When you create a share for your backups it must contain a WindowsImageBackup folder. You cannot share the WindowsImageBackup folder directly as it will not locate any backups.
- Proposed as answer by Justiin Tuesday, July 23, 2013 6:53 AM
Windows-7 64 repair disk.
Got the same message but just skipped it through the installation.
What I saw
1. Created network backup and recovery DVD
2. Booted DVD, selected network location
3. Voila image is there, but have not put the right drive yet so needed to shutdown and go back to square one
4. Repeated step 1 and 2
5. "An internal error occurred while enumerating backup sets", note there was no problem 5 minutes ago
6. refresh, putting different paths forth and back etc etc - to no avail
7. got a internal error pop up once again but pressed enter two times accidently
8. Voila moved on with the image selected despite the error.
Conclusion, there is some bug which makes the message box pop up and image not shown.
Despite of that the image is there, is detected and you can move on within the process.
Mediocre Access 2010 | (Baby) Beginner C Sharp | OK at Active Directory (2012 R2) | Fragmented understanding of DNS/DHCP | Laughable experience with Group Policy | Expert question asker on MSDN Forums
Mediocre Access 2010 | (Baby) Beginner C Sharp | OK at Active Directory (2012 R2) | Fragmented understanding of DNS/DHCP | Laughable experience with Group Policy | Expert question asker on MSDN Forums
I had an issue recently where I was getting the same error message "Internal Error occured while enumerating backup sets" when trying to restore from a 2012R2 network share. We migrated our file server from 2003 to 2012R2 (clean install on VM) earlier this year and we have gotten the same IPSec Main Mode error since the upgrade. I have been ignoring the IPSec error message because I haven't had a problem backing up and restoring machines up until this week. This week I started getting "Internal Error occured while enumerating backup sets", so I started researching the error, which led me here. We have about 20 or so "Multiple OS" images on a share on our 2012R2 file server. I immediately started removing all but Windows 7 images from the WindowsImageBackup folder based on what I read here. It did not help, I kept getting the "Enumerating Backup Sets" error. So I removed all Image folders from WindowsImageBackup and started adding them back 1 by 1, hitting "Refresh" in the System Restore window in System Recovery. They started showing up 1 by 1 as I added them, up until about Image file number 18 or so. As soon as I added that particular image folder back to the WindowsImageBackup folder, I got the "Enumerating Backup Sets" error again. I removed it again and I was able to see all of my Images again. I opened the folder contents of that particular computer's image and noticed that it had the vhd file, but it was missing most of the xml files that are normally there. I deleted the computer's folder from WindowsImageBackup and I ran our wbadmin script to pull a fresh image of that computer. Every thing is back to normal now and I can see all of my images again. Corrupted or incomplete Image Folder was the cause in this situation.
I wanted to share this, because I didn't see much about this particular reason for the error online.
-Garrett
This helped me a great deal! After 5 hours of messing about with copying a 300GB backup here and there lol!
Thanks!
Microsoft Outlook 2016 keeps asking for a password
I have Microsoft Office Pro Plus 2016 through a community college that uses office 365 and I am getting a need password every time I go into outlook 2016 on my primary computer but on my surface 3 and my developer computer it works fine
I have tried the Microsoft office recovery program that is supposed to fix this issue with outlook 2016
I have had these issues before but not as bad because normally the program will fix itself after I use the recovery program
The thing is I have my student email syncing into outlook 2016 through the exchange server through office 365
Any help would be much appreciated
Hi,
Outlook keeps prompting for password could be caused by several reasons:
- Outlook is configured to prompt you for credentials
- Incorrect password cached in credential storage
- Required Authentication Settings for outgoing server and incoming server
- Outlook Anywhere is not configured to use NTLM Authentication
- Corrupt Outlook profile
- Slow or unstable network connection
- Antivirus programs
- Shared calendars
We have a forum article discussed this issue in detail, please follow the instructions in the article to troubleshoot the issue:
Hope this helps.
Regards,
Steve Fan
TechNet Community Support
Please mark the reply as an answer if you find it is helpful.
Hello,
You should try the given below steps to fix the occurred issue:
- Close "Microsoft Outlook" >> Click on "Start" button >> type "Credential" in the search box >>you will then see 'Credential Manager' >> Click on "Credential Manager".
- Under "Generic Credentials", you will most likely see an entry that has Outlook in the name.
- Delete it. In fact, you can delete all the entries in Generic Credentials if you like.
- Close Credential Manager Window and start "Microsoft Outlook".
- If it asks for a password, enter the password and check for it to remember the password.
- A new entry will be created in the credential vault with your latest login and password.
- Problem solved.
When I was searching about your issue on the Web, I found an informative article on Outlook is asking for password.
Thanks & Regards
Clark Kent
I did what you said to do and today I went to open outlook and it did the same thing again and said need password
And so I tried the credentials thing in the control panel and it would not work
Still asking me for a password
Any other recommendations?
Hi,
Outlook keeps prompting for password could be caused by several reasons:
- Outlook is configured to prompt you for credentials
- Incorrect password cached in credential storage
- Required Authentication Settings for outgoing server and incoming server
- Outlook Anywhere is not configured to use NTLM Authentication
- Corrupt Outlook profile
- Slow or unstable network connection
- Antivirus programs
- Shared calendars
We have a forum article discussed this issue in detail, please follow the instructions in the article to troubleshoot the issue:
Hope this helps.
Regards,
Steve Fan
TechNet Community Support
Please mark the reply as an answer if you find it is helpful.
I'm having the same issue as well. Strangely enough, 4/5 users that I have migrated to 2016 have worked flawlessly. Unfortunately, just the one user is now having the repetitive password prompt. When opening Outlook, the status at the bottom will say "Connected to Exchange", but then a few seconds later the password prompt appears. The user's mailbox is migrated fully into 365 and the user account is also fully in sync with AzureAD/Local AD. The Outlook profile has been removed/recreated several times now and the credential manager has all the stored accounts removed.
Still drawing a blank. Anyone?
Here's one thing to check that hasn't been mentioned but I ran into. Outlook 2016 was requiring a password whenever I rebooted, and I discovered that the Generic Credential being created in Credential Manager had a Persistence setting of "Session" meaning it only lasted as long as I was logged on. I never found out why the credential was being created that way but I was able to fix it by taking a screenshot of it, deleting the credential and manually creating a new one, which then had a Persistence of "Enterprise".
-Peter
I am having the same issue , Outlook 2016 connecting to Office 365 / Exchange Online.
Prompts for password after reboot or closing Outlook , typically prompts twice in Outlook and once for Skype for Business to make the Exchange integration connection.
I've tried credential manager, mine session is set to Enterprise. We do not have SCP autoconfiguration URLs exposed publicly so I excluded those look up in the registry. Can't seem to shake this issue. No problems when using Outlook 2013.
- Proposed as answer by Arjan Coolegem Friday, July 22, 2016 1:43 PM
Hi Clark,
Thanks for the tip. My Outlook 2016 password issue has been resolved following the steps you provided.
Thank you!!
- Close your outlook.
- Type in "Credentials Manager" in search window.
- Click on Windows Credentials.
- Find entry for your email account and click on Edit. You probably will see "Persistence:Local computer"
- You need to remove entry for your account.
- Open Outlook and when you prompted to enter credentials – enter password and click on Save Password.
- Go back to credentials manager and confirm that settings for Persistence set to Enterprise : "Persistence: Enterprise"
We use basic authentication with a Load Balancer in front of our Exchange 2010 Servers.
Outlook 2016 (in another domain as the Exchange Servers / in no domain) keeps aksing for a password. Solution:
Username: UPN
Using the UPN -> no problems so far
- Proposed as answer by mdaas Friday, March 3, 2017 9:08 AM
I have a mixed environment of Exchange 2010 and Exchange 2016. I've had a software assurance tech support case open with Microsoft for a month plus. So far even they can't figure it out. Definite major bug here. Be advised. Don't adopt Exchange 2016 until it's fixed..
- Edited by ZackinMA Tuesday, February 16, 2016 2:11 PM
What is the UPN?
I know my domain\username , and have access to the my directory details. What am I looking for when you say UPN?
We have Exchange 2010 on premise mixed with Exchange Online (O365). I'm on O365.
- Proposed as answer by RandomNumber5 Friday, November 8, 2019 8:52 AM
After updating to the latest Outlook 2016 version (16.0.6568.2036), which solved the awefull POP3-Bug, it introduced a new bug. We had a comma and an umlaut in a POP3 password. After the update Outlook was not able to download the emails anymore. It stated that the username or password were invalid. I was still able to login in with that password using the mail web page of my provider. Only after the comma and the umlaut have been removed Outlook was able to connnect. It worked fine before the update.
These are two major bugs in a row. I miss the times when updates were delivered on floppys. This was so much more expensive for the software vender and therefore the updates were better tested. Now the work and cost are only with the enduser.
I've seen this a lot and many of the ways described have fixed it for me in the past... whacking credentials and the like.
This time I encountered the problem when upgrading a system to Office 2016/O365 from Office 2010.
I originally...
- Removed Office 2010 (standard install, using O365)
- Installed Office 2016 (O365 install)
- Ran Outlook
- Prompted to login, it started downloading my mail, but kept popping up password prompt
I then tried all the usual stuff. No good.
Then I realized... "Wait... I never created a new mail profile... it just used my old one and re-prompted me for login."
So this time, I closed outlook, re-removed all my credentials, then deleted the mail profile.
Then launched outlook, re-created mail profile... it prompted me once for the login as it always does post-setup... and boom. Worked.
- Proposed as answer by muscleflex Wednesday, June 6, 2018 10:12 AM
Rick Nelson
I Know this is an old post, however It still comes top of Google and many people like me will find this very frustrating. Here however is the correct fix after long time of looking
[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\AutoDiscover]
"domain.com"="c:\\auto\\autodiscover.xml"
"PreferLocalXML"=dword:00000001
With HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover
for Outlook 2010
You must make this solution more robust by adding these registry entries:
"ExcludeScpLookup"=dword:00000001
"ExcludeHttpsAutodiscoverDomain"=dword:00000001
"ExcludeHttpsRootDomain"=dword:00000001
"ExcludeSrvLookup"=dword:00000001
"ExcludeHttpRedirect"=dword:00000000
"ExcludeSrvRecord"=dword:00000001
The only lookup type that will be used now, is HTTP Redirect to the XML file. If this fails, there'll be no Autodiscover.
This is an excerpt from my documentation after having implemented this solution twice with different forests, not Office 365.
If you input that and open outlook. No more password prompt. Export and push out to all other machines on the network.
- Proposed as answer by willstay Thursday, January 24, 2019 11:20 AM
This was useful!
Scenario:
- Windows 10, Office 2016
- Skype for Business configured to start automatically
- Skype and Outlook work fine;
- when the computer drifts off to sleep, and you authenticate back into Windows, OUtlook prompts for credentials
If Skype for Business is NOT running automatically, and you repeat the above, Outlook doesn't request credentials.
Any root causes...? Running July 2016 updates for Outlook and Skype for Business.
It's a straight forward fix.
1. Go to credential manager and manually re-enter the password in all of the locations where the users email password is stored.
2. Go to "C:\Users\*user*\AppData\Local\Microsoft\Outlook\" Locate the .XML file. "f0a4256167a8597a89das6hf01c6bb1b - Autodiscover.xml" <-- or something like this. Move this file or rename it.
3. Launch Outlook again and you should not get any further prompts. The Autodiscover.xml file will be recreated automatically.
- Proposed as answer by Nipun Shedhani Wednesday, September 14, 2016 9:01 PM
Thanks Bilboswagins..... Your suggestion worked. I have windows 10 with Office 2016, Following did not work:
- I tried to delete my outlook profile created a new one!
- Deleted Credentials from Credential manager!
- Profile Security Settngs enhancements,
- Annoymous logins selection.
- Checking Do not Prompt for UserName Password.
Regards,
Nipun
- Proposed as answer by OTEKO Wednesday, February 15, 2017 3:04 PM
I cant believe how long its taken me to find this answer, but am so thankful for it!!!
Worked for Outlook 2016, connecting to Exchange Online (just migrated) setup in a Hybrid 2010 On-Premise Exchange.
Thanks Again
Hi,
The problem is AD side ! ( Outlook 2016 + Exchange 2013 only )
On these password prompts, you'll notice it's authenticating for the users e-mail address.
Outlook 2016 does all the configuration automatically, and expects to find everything it needs via auto discover. Putting it simple, the user's UPN must match their e-mail address.
You need to change users logon names to make them match with their email addresses.
If your email domain is different from your organisation domain you first have to add the UPN suffix (which is the actual e-mail address domain name) to the Active Directory Domain and Trusts. Instructions are available here: https://support.microsoft.com/en-us/kb/243629
After adding your e-mail domain to the UPN suffix list. When you go in to "Active Directory Users and Computers", and view a user's properties, you'll notice in the UPN section, you can drop it down and change it from internaldomain.local, to contoso.com (using my example domains).
Then you need to change the logon name to make it match the email address.
DO NOT CHANGE the old DOMAIN\Username setting !!!!!!!!!!!
After that the user will authenticate with it's email address and password and autodiscover will work properly with no password prompts.
It's a straight forward fix.
1. Go to credential manager and manually re-enter the password in all of the locations where the users email password is stored.
2. Go to "C:\Users\*user*\AppData\Local\Microsoft\Outlook\" Locate the .XML file. "f0a4256167a8597a89das6hf01c6bb1b - Autodiscover.xml" <-- or something like this. Move this file or rename it.
3. Launch Outlook again and you should not get any further prompts. The Autodiscover.xml file will be recreated automatically.
After dealing with this minor annoyance for some time now, I have tried everything under the sun to fix this stupid issue. Your solution was spot on. Thank you very much, Very appreciated!
+1
My situation when I experienced this is probably subtly different to others here. I'm a home user with 2 outlook.com accounts, Windows 10 and Office 2016.
I've resolved the issue but had to go through many hoops. It started because I received an "unusual sign-in activity" alert for one of the email accounts, the result of which disabled login (incidentally I traced the irregular sign-in attempt to the MoD in London).
The first thing I did was reset the password. I was able to re-establish access to the account through OWA and the Android Outlook app but not through Outlook 2016.
One of the hoops I went through was online support with a Microsoft Tech who took control of my PC, spent an hour trying to fix it and had to escalate - I couldn't hang around any longer waiting for them (Microsoft - if you're interested, the case number is 1363449386).
Following a difficult night's sleep (tech has a lot to answer for) I attempted a "soft" sledgehammer approach using a number of the steps listed in this thread. What did the trick was to:
- Remove all email accounts from Outlook
- Delete all Outlook profiles (there was only one)
- Delete all credentials from Credentials Manager (both Web and Windows)
- Delete all *autodiscover.xml entries from "C:\Users\*user*\AppData\Local\Microsoft\Outlook\"
- Add the account back in to Outlook
Which of these actually resolved the issue for me I'm not certain however I've a feeling it was deletion of the autodiscover files.
- Edited by Gary the data guy Sunday, November 20, 2016 11:48 AM
Hi,
I have the same scenario, and we are working with the last november release, we tried the old realeases.
I haven´t problem with the user account, the problem is when you add a shared mailbox in Outlook, it is asking for password until your press Cancel button, but the shared mailbox works perfectly.
if I stop Skype for business, the I haven´t any problems.
did you find any solution???
Thanks,
- Edited by bbr Tuesday, January 3, 2017 1:08 PM
I did exactly the opposite - I've unchecked the data encryption and Outlook stopped asking for credentials :)
Thanks for the hint.
- Edited by KRWudtke Tuesday, January 24, 2017 10:29 PM
@SKYTOUCH Solutions INC - There are like 10 different solutions above your post. Which one of them is so terrible and killed your PST?You can use ScanPst to try to fix the corrupt PST file.
- Proposed as answer by SilentRick Tuesday, February 14, 2017 7:20 PM
- Unproposed as answer by SilentRick Tuesday, February 14, 2017 7:20 PM
We use basic authentication with a Load Balancer in front of our Exchange 2010 Servers.
Outlook 2016 (in another domain as the Exchange Servers / in no domain) keeps aksing for a password. Solution:
Username: UPN
Using the UPN -> no problems so far
This fixed it for me (Non domain joined W10 laptop with Outlook 2016 connecting to Exchange 2010)
Using UPN, that is username@domain.local, in instead of domain\username and no more password prompts for me.
I have Microsoft Office Pro Plus 2016 through a community college that uses office 365 and I am getting a need password every time I go into outlook 2016 on my primary computer but on my surface 3 and my developer computer it works fine
I have tried the Microsoft office recovery program that is supposed to fix this issue with outlook 2016
I have had these issues before but not as bad because normally the program will fix itself after I use the recovery program
The thing is I have my student email syncing into outlook 2016 through the exchange server through office 365
Any help would be much appreciated
So a bit late for answer but Try this...
MicrosoftAccount\Blah@Outlook.com
Basically The Domain is MicrosoftAccount\EmailAddress It is the same as if you were remote accessing your PC. I had the same issue myself and did try chaning e-mail account and that wasn't working. It magically started showing up for one of my Microsoft e-mails.
Try MicrosoftAccount\EmailAccount for name... I had same issue magically started happening last week. I got it working by using same credentials I use to access PC Remotely. I never had this issue before and just started. I removed account and that was a mistake when all I really needed was the name change.
IE
MicrosoftAccount\Flocker@outlook.com
- Proposed as answer by fixfinder Tuesday, April 4, 2017 1:35 AM
I know this thread is a bit old but I had this issue on a Windows 10 machine recently and the resolution was something that hasn't been mentioned yet so this might be of use to some.
In our case it was due to Modern Authentication being turned off.
Adding the right things to the right place is detailed here:
https://support.office.com/en-gb/article/Enable-Modern-Authentication-for-Office-2013-on-Windows-devices-7dc1c01a-090f-4971-9677-f1b192d6c910
Hope this helps someone else out as it's been driving me mad for days!
I had this problem and it's now fixed, the issue was the application password option.
https://support.microsoft.com/en-gb/help/12409/microsoft-account-app-passwords-two-step-verification
Go to the above site, generate a new app password, use it in place of your normal password in the outlook setup process and any pop up boxes.
Your normal password will work fine in the web view
Using the application password and not your normal email password solved it for me.
- Proposed as answer by Mick_B Sunday, April 23, 2017 8:56 AM
I have run the MS Support and recovery assistant for office 365 that you can download .
Selected the option for password prompting and all checked out apart from one issue.
Autodiscovery.....
Attempting to test autodiscover service for "xx.xx@company.com".</
We found some problems retrieving your Office 365 user settings (autodiscover).</
Incorrect username or password.<Please try again or verify your username and password from Office 365 Portal</Hyperlink>. If you cannot sign in, contact your Office 365 admin for help.
We received a response other than the expected HTTP Status 200 OK. Status: 401.</
R
Attempting to retrieve SCP URLs
We couldn't find any SCP urls
Attempting to test the autodiscover service using the method: HttpsAutoDiscoverDomain
We failed to retrieve user settings (Autodiscover) by method: HttpsAutoDiscoverDomain
Attempting to test autodiscover service with autodiscover endpoint "https://autodiscover.xx.company.com/Autodiscover/Autodiscover.xml
We couldn't retrieve your Office 365 user settings (autodiscover).</
Hello everyone.
In all that I have read in this subject, I have tried every one of his opinions and I do not have positive results.
My case is different, I have 600 mailboxes to migrate under a hybrid environment.
On the testconnectivity.microsoft.com site I have taken the <server> ID Server + @ my domain .com tag
These steps I handle very well.
The case is when the mailbox mailbox migration ends, the user does not notify you of the change that will be made in Outlook, and the user only enters through the Office 365 OWA.
In Outlook it is created a new profile, and it is marked to request a profile, and it is manually configured the user's account, at the end of giving the next button the sale "Windows Security (not Respond) does not allow user data entry .
In an example:
In a virtual machine configure a mail account in outlook 2010 and in another virtual one with outlook 2013 and I worked the manual configuration, two users migrated to Office 365, but in their physical equipment does not allow it.
Who knows how to solve this process?
Because I do not want to do the pain of formatting each PC just for the Outlook case.
Greetings.
Hi Clark,
Thanks a lot for your post. It works!!
Regards,
Nithiya
I know this thread is quite old but I recently ran into this as well. . For me I am using O365 through my contracting company and not through the place I work at. Go to File -> Office Account. My O365 account was logged in for the place I contract with and not for my contracting company. Switching accounts to the same account my contracting company provided me stopped the password prompts.
Basically make sure your office account is logged into the account that your email is associated with in Outlook.
We had the exact same issue and here is the solution - works every time!
You need to use your activesync username, not email address and not domain login.You start Outlook and when it prompts you for the password, select other user and enter your ActiveSync name - starts with the server or hosting domain followed by a \ then the username.
example: Username: Exc091\john.doe_tempeaz.com
Then you put your login password and check the remember password box and then hit enter on the keyboard.
Works every time!You may need to contact the hosting provider for the activesync username - unless you have admin rights.
Thanks,
DC
- Edited by mmast Tuesday, May 30, 2017 6:20 AM
This worked perfectly for me.
Thanks
I did the above steps (i delete all entries in generic Credentials), and outlook still asks for password.
I get back to Generic credentials and edit the newly created entry and reenter user name.
This solve the problem for me.
- Edited by Pete Newcomb Friday, June 16, 2017 5:53 PM Clarification
Outlook 2016 on my laptop accesses email through my gmail account. Whenever I change my gmail password, I have to change it in the Outlook account settings as well.
Today I did not change my password, but I had reconfigured a few things in gmail regarding security. Besides changing my phone number, I had turned off "access for less secure apps."
After that, Outlook kept asking for a password and nothing worked. Looking at my gmail account online, there was a message from gmail that someone had turned off "access for less secure apps."
I turned that back on. Outlook is working fine again.
I'de the same problem.
In my case the only solution was:
1) Remove office 365 account from Outlook
2) Unistall office
3) Reinstall office
4) Recreate office 365 account on Outlook.
Regards,
Thank you - this worked for me, but there was an auto-generated hidden folder called 16 that I had to rename as well as the xml file:
i.e. C:\Users\*user*\AppData\Local\Microsoft\Outlook\16
Windows 10 and Office 2016 are still a bag of spanners IMHO. Nothing was broken, why did they try and fix it?
- Edited by Derbyp Wednesday, July 19, 2017 8:22 PM
- Proposed as answer by BirtyBassett Wednesday, January 3, 2018 8:03 PM
I've tried every suggestion on this and other threads: clearing credential manager, running the Office troubleshooting tools, deleting and trying to recreate profiles, registry edits, etc - nothing works.
I even sat on the phone with Microsoft technical support for 90 minutes until that tech gave up and kicked it up a level. I'm now waiting for a callback.
I decided to try one last thing. For reference, I have two email accounts and both were causing problems.
I tried one more time to recreate my account in Outlook - no luck. Then I fired up the Windows 10 mail app and added the account - it worked. I then immediately tried to go back to Outlook and recreate the account (it had failed not 10 minutes prior) - and it worked. Immediately. I could not believe it.
Just to make sure I tried my other account. I tried to create it in Outlook - failed. Created it in the Windows 10 mail app - success. Went back to Outlook - it worked right away.
ymmv but after trying everything else it sure seems to me that the Windows 10 Mail app manages to reset some setting that Outlook is not smart enough to resolve.
David M Nicholas Power Computers, Inc
To get rid of this error follow these steps.
1) Go into credential manage
2) Select windows credentials
3) Scroll down to the one that shows MicrosoftOffice 16 and click on it
4) Select edit
5) Enter in your username that you sign into the computer with and enter in the updated password that you just changed for your windows log in
6) You may have to open and close outlook a couple times but it will recognize your updated password and the needs password message will be gone.
- Proposed as answer by rnenjoy Friday, October 13, 2017 3:17 PM
I Know this is an old post, however It still comes top of Google and many people like me will find this very frustrating. Here however is the correct fix after long time of looking
You likely have thse two registry settings:[HKEY_CURRENT_USER\Software\Microsoft\Office\12.0\Outlook\AutoDiscover]
"domain.com"="c:\\auto\\autodiscover.xml"
"PreferLocalXML"=dword:00000001With HKEY_CURRENT_USER\Software\Microsoft\Office\14.0\Outlook\AutoDiscover
for Outlook 2010You must make this solution more robust by adding these registry entries:
"ExcludeScpLookup"=dword:00000001
"ExcludeHttpsAutodiscoverDomain"=dword:00000001
"ExcludeHttpsRootDomain"=dword:00000001
"ExcludeSrvLookup"=dword:00000001
"ExcludeHttpRedirect"=dword:00000000
"ExcludeSrvRecord"=dword:00000001The only lookup type that will be used now, is HTTP Redirect to the XML file. If this fails, there'll be no Autodiscover.
This is an excerpt from my documentation after having implemented this solution twice with different forests, not Office 365.
If you input that and open outlook. No more password prompt. Export and push out to all other machines on the network.
---------------------------------------------------------------------------------------------------------------------
Thanks, Bodsworth - KUDOS to you!
the underlined section above helped me in my situation, the tech that setup his outlook prior to migrating to Office365, put that in the registry and it was causing all kinds of headaches with one client. I removed the entry and moved the folder it was pointing to , then recreated the profile and no more prompting for password.
I have the same problem connecting to OUTLOOK.com free account from Outlook 2016.
NONE of the items outlined worked. I don't even have options to change the settings they are grayed out in outlook/account/settings.
I have another account same setup, no issue.
It seems to be an issue with sending mail not receiving. ALSO if I ignore the problem it disappears after some time. hours/days/etc... but it comes and goes.
I encounter this problem in outlook 2016 and have tracked down the behavior to
1) it is another email account that is part of my outlook 2016/exchange 2016 profile (I have 3 exchange accounts in the profile; one is for testing; one is my main company email, the other is another company email. TWO of them use the same username, with different domains.
My main account is kad***@ourdomain.com. My account name is kad***@ourdomain.com.
The other email account is named as kad***@otherdomain.com. The domain account name is otherdomainxx@ourdomain.com (the xx are two arbitrary characters to distinguish the username from the otherdomain name). BOTH are domain accounts in ourdomain.com. otherdomain.com and ourdomain.com are both serviced by OUR DNS server.
2) The credential problem crops up immediately when you try to open a PDF attachment that I receive in the kad***@otherdomain.com email box (with adobe). The PDF opens, but the credential prompt immediately follows (and despite what you type at it, it will not go away until you stop and restart Outlook)
The outlook version is 16.0.8431.2046 32-bit
Problem has NOT been solved with update to Version 1709 (Build 8528.2139) (Released October 16 - I just updated now)
- Edited by Keith Dorken Windview Monday, October 23, 2017 7:39 PM
Issue: Outlook 2016 prompts for credentials when opening attachments [WORKAROUND]
Last updated: Oct 12, 2017
ISSUE
Outlook 2016 On Premise users are prompted for credentials when opening email attachments. This occurs after updating to Current Channel build 16.0.8431.2079.
STATUS: WORKAROUND
Do the following to revert to an earlier build:
-
Open a command prompt window.
-
At the command prompt, run the following commands:
cd %programfiles%\Common Files\Microsoft Shared\ClickToRun\
officec2rclient.exe /update user updatetoversion=16.0.8326.2107
Note: If 16.0.8326.2107 is unavailable, refer to Version and build numbers of update channel releases to find another recent version for your respective channel.
- Edited by ponyandcarriage Friday, October 27, 2017 6:05 PM
Could please anybody from Microsoft fix this? We have legal SW and we've paid NOT to have issues like this.
I tried all the 20 steps to fix these Outlook 2016 on Windows 10 (on an Exchange 2010 on premise Server, meaning SBS2011) pop ups when opening attachments. Nothing helped till the last answer from ponyandcarriage.
The problem with a downgrade is that I cannot downgrade all computers and stop them from upgrading. What happens is that computers eventually do updates after the next reboot if you don't prevent this in outlook. But without updates... Not a good situation...
I tried all the 20 steps to fix these Outlook 2016 on Windows 10 (on an Exchange 2010 on premise Server, meaning SBS2011) pop ups when opening attachments. Nothing helped till the last answer from ponyandcarriage.
SBS2011 doesn't seem to set up autodiscovery by default. After adding this in DNS on the SBS server Outlook 2016 was able to set itself up. Add a new primary zone to your forward DNS called autodiscover.maildomain.com (where maildomain.com is your internet mail domain) then create a new A record in that zone with no host name (meaning it will point to the zone name) with the IP address of your SBS server.
If that doesn't solve your issue I had already updated the users UPN to @maildomain.com. This is done by adding @maildomain.com to domains and trusts then changing the drop down in the account tab of the user or mail in ADUC or EMC respectively.
We all had patched the Exchange to be up to date recently in case that is also a factor (SP3 rollup 18 form memory)
This worked for me.
https://www.liquidweb.com/kb/how-to-set-up-email-in-outlook-2016/
after fighting this issue with random people we have migrated from on prem to O365 for months this was the fix! Thank you!
- Proposed as answer by Edwin.Castellanos Monday, January 15, 2018 3:51 PM
- Edited by Edwin.Castellanos Monday, January 15, 2018 3:52 PM
Allow access to the less secure apps in your gmail account https://myaccount.google.com/lesssecureapps
Then just try configuring outlook again. it should work
Allow access to the less secure apps in your gmail account https://myaccount.google.com/lesssecureapps
Then just try configuring outlook again. it should work
Okay so first of all, I tried all the solution bellow, and then I finally figured out what was going on :
You have to check one thing at first : If you are using two-step verification, DISABLE it on your Microsoft account and this will work ! You are only prompted for your password once, then it works normaly !
I suppose you can re-enable it, but only after you are connected !
Hope this will help you !
this might be a long shot, but i've seen this fix other things.
go into AD and reset your password to same as current (unlock account is need be). then go remove all the entries in cred manager. reboot. then let outlook and skype rebuild the cred entry.
Hello,
We had similar Outlook 365 client prompt for password issues with all mailboxes at Office 365 in an Exchange 2016 hybrid scenario. Our fix was updating Outlook Anywhere settings to use only NTLM following steps detailed here:
https://www.pei.com/2016/07/exchange-authentication-prompts-from-2013-back-to-2007-public-folders/
We did not have public folders and had recently swapped over from an Exchange 2010 on premise server to 2016 so the settings were different and that caused the password prompt issue is apparently difficult to diagnose with all the possible issues.
-larry
This one worked for me.
I deleted add cached passwords related to any Outlook version.
I have Windows 10 Home and Office 365 Personal. I formerly had Office 16 installed through an employer. When I left the employer, I switched to Office 365. I use the downloaded apps, not the online apps.
This all started when I changed my password on account.microsoft.com.
Got OneDrive and the Office apps working just fine, but couldn't get the Outlook app to stop asking me for a credential that looked like it was using my Laptop name as a domain name. Tried my Microsoft password, tried getting and using an app password, tried the Windows password I use to log onto the laptop.
I tried EVERY suggestion on this page and none of them worked. I was pulling my hair out (and wasting many hours and losing significant sleep).
Then I remembered I had created an alias for my outlook.com account. So instead of setting up an account in Outlook with my primary outlook.com account, I used the alias. IT WORKED INSTANTLY! And even better, in Outlook it displays my primary outlook.com address, not the alias.
- Edited by CandrevaConsulting Monday, September 24, 2018 1:42 PM typos
I just upgraded from Office 2013 Pro to Office 2016 Pro and suddenly my Exchange account kept prompting for password.
Connected via VPN to local area network that my Exchange was on, went to Account Settings, Change, More Settings, Security and Unchecked Encryption: Encrypt data between Microsoft Outlook and Microsoft Exchange.
Prompted for password once more and this time it received it, no more promptings. I then turned Encryption back on and it's fine.
We have this week a problem regarding office365 and Office 2016 and keeps asking for password.
We have migrated PC's to another domain, and copied info from user profiles to the new domain.
Our solution was to rename this folder in the user profile:
%appdata%\local\packages\Microsoft.AAD.BrokerPlugin...
Come back and mark replies as answer if they help, and help others with the same problem. If this post is helpful please vote it as Helpful on the left side.
- Go to Registry Edit on each computer (Do not run as administrator)
- Go to the following path<g class="gr_ gr_12 gr-alert gr_gramm gr_inline_cards gr_run_anim Style multiReplace" data-gr-id="12" id="12">: :</g> HKEY_CURRENT_USER\Software\Microsoft\Office\16.0\Outlook\AutoDiscover
- Set the Registry Edit: ExcludeExplicitO365Endpoint to <g class="gr_ gr_13 gr-alert gr_gramm gr_inline_cards gr_run_anim Style multiReplace" data-gr-id="13" id="13">Value :</g> 1
i have do some research with your reply and i have foudn this :
https://support.microsoft.com/en-us/help/2212902/unexpected-autodiscover-behavior-when-you-have-registry-settings-under
For information with our exchange, we use SRV record discovery
No problem with outlook 2013, just 2016 or 2019
Thanks John_boi !!!!
- Edited by troublestarter Wednesday, October 17, 2018 11:51 AM
If Multifactor Authentication is activated (MFA), Outlook requires generating an App Password.
You have to log into your Office.com portal: https://portal.office.com/account/#security (under Security and Privacy) and create an App Password, then enter that password when Outlook prompts for it. It's not the password you enter when logging in normally or online.
I had to do the same for my Xbox account once MFA was activated which was much worse because I couldn't copy and paste the password and had to use the controller to enter it. Ugh.
More info here:
https://support.office.com/en-us/article/create-an-app-password-for-office-365-3e7c860f-bda4-4441-a618-b53953ee1183
Luke Chung
Microsoft MVP
President of FMS, Inc.
Blog Facebook Twitter
Credential Manager worked for me.
Basics:
My mailbox was migrated from Exchange 2016 to O365 a few days ago.
This evening, I was prompted to change my work password which I did from my work laptop.
For my work laptop - everything worked fine.
Personal PC on a lab domain had the issue:
Outlook 2016 connecting to my work email using work domain credentials.Outlook 2016 prompted for password (as it should) but would never take.
Found this Thread:
Closed Outlook.
Went to Credential Manager and did an Edit of the Account (was already set to Enterprise).
I updated the password and saved.
I Opened Outlook and all is working fine.
Using the primary email instead of the alias worked for me. The alias used to work fine but occasionally got into a state where it kept re-prompting for the password.
Today I gave up and deleted the account and re-added it with the primary email and it worked. It does display the alias in Outlook which is what I want. This is backwards from your situation, Candreva. Thanks.
Sincerely, Manny A.
I read about 40 different sites looking for this answer & found that MAPI over HTTP was the root cause. For testing purposes, you should read this article:
https://blogs.technet.microsoft.com/rmilne/2017/01/25/how-to-disable-mapihttp-for-a-single-mailbox/
Add to that list, adding your enterprise outlook account to the microsoft mail app on your work computer.
I did this a few days ago for testing purposes and today my outlook went really pear shaped, had to remove my account completely from the mail app
ThomasMuc2, where do you set that username? (And why would a username affect anything?)
You mentioned basic authentication, is that a laptop setting, if so, where is it set?
- Edited by PReinie01 Wednesday, June 5, 2019 4:25 PM Address the person I'm asking the questions of.
ThomasMuc2, (and @jacecole) I found out what you meant when I looked up UPN.
To anyone, UPN is User Principal Name.
In this case, it basically means to use your email address. At our company that takes the form of Firstname.LastnameATemaildomain.com (emaildomain is often the company's name and I had to use AT instead of the @ sign because "my account hasn't been verified so I can't put in emails and URLs).
@bryanGee After deleting the credentials you have to sign out of the account (restart computer, etc) and sign back in before you can test the solution. (Windows 10 shutdown from the start menu may not work as it hibernates the computer to make it appear that it starts up faster from shutdown. Then again, I think it also signs you out so maybe it will work.)
It seems somehow, something is remembering whatever credentials are there, getting them from cache or a buffer somehow but that info is cleared on restart, Shift-Shutdown or sign out/in.
Changing the AD password may help too (instead of clearing credentials) as that causes the new password to overwrite the one that's there.
It may be that you have inadvertently reset Chrome's security measures.
If you have Gmail through Google Chrome and use Microsoft's Outlook 2007, then to enter Outlook without having a pop3 window from asking for the password, click on your Google icon, then click into security, and then scroll down to the "Less secure app access" window that shows the padlock. If the Third-party access row has a black circle indicating OFF, then click on "Turn on access (not recommended)", and at the next screen position the slide button to "on". Exit back, and there should now be an orange circle On with an exclamation point.
Open up Outlook. If the Inbox does not populate, then open up your email settings and make sure that your gmail User ID and Password are entered correctly.
- Edited by RwBug Saturday, September 21, 2019 6:29 PM
I have this problem with Exchange 2016. Outlook 2016 clients prompt for password upon launch. Most prevalent after a reboot or signing out/in to Windows. Prior versions of outlook (2013 and 2010) do not do this in testing. It's only 2016. This is impacting our deployment plans for Office 2016.... as in we're not!We are experiencing this same issue. Same outlook 2016 client. Move to exchange 2016 from 2010 and now get the outlook client password prompts. Everything is on-premise. Were you able to resolve this ?
I have this problem with Exchange 2016. Outlook 2016 clients prompt for password upon launch. Most prevalent after a reboot or signing out/in to Windows. Prior versions of outlook (2013 and 2010) do not do this in testing. It's only 2016. This is impacting our deployment plans for Office 2016.... as in we're not!
We are experiencing this same issue. Same outlook 2016 client. Move to exchange 2016 from 2010 and now get the outlook client password prompts. Everything is on-premise. Were you able to resolve this ?
I got that problem when I migrate from exchange 2016 to exchange 2019
I think we should find the solution on the server not on the client!!
Ghassan
OMG!!!! SOLVED>
You, whomever you are, are a flipping GENIUS! I have been struggling with this issue and googling everything EVERYWHERE to fix it and nothing worked.
THANK YOU very much :)
In the event that this reply goes to the bottom of this feed, here is what the instructions were:
"It may be that you have in advertently reset Chrome's security measures.
If you have Gmail through Google Chrome and use Microsoft's Outlook 2007, then to enter Outlook without having a pop3 window from asking for the password, click on your Google icon, then click into security, and then scroll down to the "Less secure app access" window that shows the padlock. If the Third-party access row has a black circle indicating OFF, then click on "Turn on access (not recommended)", and at the next screen position the slide button to "on". Exit back, and there should now be an orange circle On with an exclamation point.
Open up Outlook. If the Inbox does not populate, then open up your email settings and make sure that your gmail User ID and Password are entered correctly. "
The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009
I have deployed my packages into Sql Server and I am using Configuration File. As my Data Source is Excel, I have changed the connection string during deployment with Server Path. But I am getting the following errors. Actually the File Exist in Path. May I know What is cause of the issue? Do I need to give any permission to execute the package.
SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
component "Excel Source Service Contract Upload" (1) failed validation and returned error code 0xC020801C.
One or more component failed validation.
There were errors during task validation.
DTS_E_OLEDBERROR, Error Code: 0x80004005 Source: "MS JET DB Engine" Description : Path is not valid
In the Project Properties->Degugging Section, I set Run64bit RunTime to False. It started working now. Thanks for the answers
In this case, yes it is...
There is no 64 bit driver for excel. The workaround is to run the package using the 32 bit version of the execution utility.
http://technet.microsoft.com/en-us/library/ms141766.aspx
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=167907&SiteID=1
How are you running the package?
Check that the user running the package has access to the specified path...
I am running through Execute Package Utility in SQL Server Management Studio, MSDB Database. Even I have added user to the Directroy where the excel file resides.
| Amzu wrote: | |
|
My SQL Server is 64 bit Windows 2003 Server Xeon Machine. Is it a problem running the package?
In this case, yes it is...
There is no 64 bit driver for excel. The workaround is to run the package using the 32 bit version of the execution utility.
http://technet.microsoft.com/en-us/library/ms141766.aspx
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=167907&SiteID=1
In the Project Properties->Degugging Section, I set Run64bit RunTime to False. It started working now. Thanks for the answers
Thanks a lot for this solution!! I struggled with this for the last couple of days!
Regards
I was trying to migrate the same package from a 32bit to a 64 bit server and was very puzzled that the SSIS import excel package failed with errors..It was indeed very helpful!!
This will cause problems if going through a SQL Agent proxy that does not have permissions to access this folder.
If you log onto the box as admin and try to manually start the job from Agent, the job will fail with DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER- even though the same job contains file system tasks that operate correctly on the same file and folder.
I ran sysinternals procmon to verify this: procmon shows the file system tasks correctly accessing the same file that the excel driver is pointed to.
Procmon also shows an attempt to access the admin's profile temp directory, followed by "Access denied", and quickly followed by a load of an rll file to display the error dts message, and subsequently the threads are terminated and the process ends.
Because of this, the process never gets to the point where it is enumerating the ISAM reg keys (HKLM\SOFTWARE\Microsoft\Jet\4.0\Engines), nor does it ever attempt to open msexcl40.dll.
This is a bug that needs to be addressed. (win2k3 server - 32 bit)
To confirm this, I took the same process and scheduled it under SQL Agent for 1 minute in the future.
It worked perfectly.
- Proposed as answer by appootan Wednesday, July 11, 2018 7:32 PM
rahulv
It is very helpful for me....
In the Project Properties->Degugging Section, I set Run64bit RunTime to False. It started working now. Thanks for the answers
I know it's too far ago, and I don´t know who you are.. but you saved my life!!!! hehe thanks a lot! =)
- Proposed as answer by Antonio_86 Monday, March 16, 2020 5:18 PM
Thanks, Rafael. I spent few hours before following your suggestion. Still you saved me few more hours of time. Thanks, once again.
@wade_b
I had the exact same problem. We run our SQL Agents using a lower level domain account and run our SSIS packages using a Proxy Account. You are correct as Procmon confirmed it for me as well. I gave the Proxy Account rights to the profile's temp directory (C:\Documents and Settings\SQLAgentDomainAccount\Local Settings\Temp) and it worked!
Thanks!
- Proposed as answer by Brad Deem 2 Friday, November 12, 2010 4:49 PM
In the Project Properties->Degugging Section, I set Run64bit RunTime to False. It started working now. Thanks for the answers
Great!!! Solved the problem.
rbj
It works to me. Thank you!
:)
Hello rafael,
I have the same error reports but unfortunately I can't change the value of the Debug Option Run64Runtime to "False" or to be precise the value is anyway set on "False" and fix. I don't use a configuration file, does it make a difference?
I am thankful for any help.
Regards Cetin
Thanks, this works :)
Thanks a ton, I did the same as suggested and it was due to the proxy account not having privileges to the temp folder for the JET excel library to run, as i found out from procmon. Gave privileges and it started working.
it worked for me, you really saved my life :)
Thanks
Ashutosh kumar
- Proposed as answer by TomK21 Thursday, October 24, 2019 11:19 PM
I am having similar issue in 2020, the package works okay on Visual Studio but fails to run as SQL job or SSIS catalog after deployment. Please note, Project Properties->Degugging Section, I set Run64bit RunTime to False and no errors prior to deployment but errors in the server despite running in 32 bit environment. Also, i have only redeployed this package to a new SQL Server but it used to work okay on the previous Server. Again, i have mapped a drive on the Server to the file but not this errors persist.
My suspicion is that the Server cannot find the file. I will appreciate your recommendation. thank you.
- Edited by Marginal Raju Sunday, February 23, 2020 8:44 AM correction
Windows Explorer Properties Information Incorrect after 1803 Feature Update
I have encountered a number of directories that now show incorrect "properties" information after the recent Windows 10 upgrade to the 1803 Feature Update. Most directories that I have looked at still show valid information. But in some specific directories the calculated size, number of files, and number of folders is wildly inaccurate. Prior to the 1803 update, the information appeared to be valid for these directories that are now in question.
From one of these subdirectories, the "CNT +" subdirectory should include everything below it. By just taking a brief look at the immediate subdirectories it can easily be seen that they describe more utilized space, number of files, and folders than indicated in the "CNT +" subdirectory itself. In actuality, there are approximately 31K files, 4.5K folders, and a size of about 4.1G in total for the "CNT +" subdirectory where the current properties information shows just 87.2M for size with 695 files and 95 folders. The directory structure and expected files are physically present. I have walked the subdirectory structure and can see the expected components.
For some unexplainable reason, a large number of these files are not being counted anymore in the higher level subdirectories. It is not until you get deep into the subdirectory structure that the properties information becomes credible again. It just looks like in some of the subdirectories that a large number of files and folders are being ignored. I still haven't been able to figure out why. This has nothing to do with "hidden" files or other system related file information. These are just plain user files.
The subdirectories in question have been in the same structure and naming convention for years. And I regularly used the associated properties information to verify the current backup size. That is now failing miserably.
After some further attempts at problem determination, I decided to move the "CNT +" subdirectory in question to remove it from its higher level directory levels. The higher level subdirectory names were added by the backup utility just for identification purposes and do not contain any files. The "CNT +" directory is now a stand-alone directory on the same "F" drive. The properties information now shows all of the expected size, files, and folder counts.
Where the previous information under the normal directory structure displayed a size of 87.2 M with 695 files and 95 folders, as a stand-alone directory the properties information now displays a size of 3.15 G with 35,773 files and 4,543 folders. These are the expected counts.
The conclusion here is that some inadvertent limitation based upon subdirectory structure has now been encountered. Prior to the 1803 Feature Update I did not see this occur. There is nothing wrong with the actual contents of the file directory and its components. There is a problem with the current method being used to calculate the "properties" information.
The normal directory structure on hard drive "F" was --
RBackupSets
RProject_10
Backup Set 2018-05-19 232221
E
Business Info
CNT +
(Following subdirectories)
Hi,
Considering the Update is released recently, if the issue persists, you could try the built-in "Feedback" tool to submit the issue on your side.
Thank you for understanding.
Best Regards,
Tao
Please remember to mark the replies as answers if they help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
Tao,
I had recently found the "Feedback" info for Windows 10 and have logged this information and detailed supporting documentation under the "Files, Folders, and Online Storage" category. Now waiting to see if any further follow-up comes from the appropriate support group.
Thanks for your follow-up response for this.
This has been reported for a few weeks now by myself and others. The bug exists in all versions of Windows 10 from 1803 on to the RS5 beta releases. There appears to have been no official response from MS to any of those feedback reports.
The bug itself appears to be an issue of the total path length, not the number or nature of subdirectories. But, of course, the more subdirectories one has, the more likely it is to have a long pathname to encounter this bug.
Disabling or enabling long filename support does not affect this behavior.
Hey Grant,
OK, thanks for your related comments. I had come to a similar conclusion as to a probable cause based upon moving the subdirectory to remove the top three levels. The result was accurate properties info. So it was looking to me like a potential total path length issue but not much way to be able to completely prove that.
I did notice a few other somewhat similar problem reports in the "Feedback" reports when I filed my report and supporting documentation about this problem. I was glad to see that others had been reporting something that seemed quite similar.
Now if MS will only wake up and address it.
Does this also affect any scripting that would be ran from the root of the drive and use a path of that same length?
from an "f:\" prompt can you do a simple dir of this directory?
something like this:
dir "RBackupSets\RProject_10\Backup Set 2018-05-19 232221\E\Business Info\CNT +"
"The only problem with troubleshooting is that sometimes trouble shoots back." "Network design is just like a stroll in the park. Jurassic Park, that is."
I tried a few tests with the "dir" command. Running the command as specified only listed the specific files and directories in the "CNT +" subdirectory. That information was correct as displayed.
I then added the "/s" operand and piped the displayed information into "more". I didn't go through the entire set of directories (There are about 35K files involved) but the "dir" command did appear to be walking through expected subdirectories and displaying the right contents for each.
Just installed the recently released cumulative update for Windows 10 at 1803 - KB4284835. Same problem still exists.
This problem has been reported via Microsoft Feedback for Windows 10 by me and others. Microsoft Support apparently doesn't read that information either. No response and the problem still exists.
- Edited by D Tun Sunday, June 17, 2018 2:40 AM
I'm having the same problem in 1803. Seeing it in a folder on my desktop. Drive is Samsung 970 Pro SSD.
The folder "!inbox" is reporting 379 files, 43 folders. When I open the folder and check the first subfolder, "!!C DRIVE", the value is 379 files, 34 folders. When I select all the subfolders (the peers of "!!C DRIVE"), the result is 29,377 files, 3,699 folders.
Based on this example, it seems like the enumeration for the "!inbox" folder is throwing a hidden exception or erroring out in the enumeration of the first subfolder.
This is a dangerous issue. I'm just wondering how it slipped past QA.
I'm having the same problem, and also in the midst of migrating a client. I was wondering why the folder size was so inconsistent. Initially with SharePoint, when files were uploaded, the size of Office documents was changing, but discovered that is by design. And now after moving files from a Win8.1 machines to an external drive, then connecting the external drive to a Win10 (with 1803 update), folder sizes mismatched. I thought I'd been up for too many hours straight!
The only way I can verify the number of files and total file size is running a "dir /s /a" which will give you a total number of files in that folder as well as sub-folders. The "/a" will include files that have attributes set, e.g. hidden files.
Hope this issue gets resolved soon Microsoft!
Other posts confirm that this appears to be a long path issue.
Why this matters:
1. The potential for loss of data seems very real. One scenario: a folder containing a set of nested folders forming a long path that breaks folder properties, with no files in any of the folders. This top-level subfolder is followed by other subfolders with thousands of files. Folder properties would show 0 files thanks to this bug. User shift-deletes the root folder thinking it's safe and watches in horror as their data is purged.
2. Browsers and modern dev tools like npm create these paths all the time. This is not rare or unusual.
- Proposed as answer by Chris From France Sunday, August 12, 2018 11:28 AM
For me I worked hard for 220.
Use the soft like Long Filename Finder or Long Path Tool 5 or Too Long Paths Detector
I have a Windows 10 Pro that I bought from Microsoft Store. It is updated to Version 1803 Installed 10-May-18 OS build 17134.191.
On one of my my HD I have a Main Folder with subfolders. File Explorer reports the size of this Main Folder size as 4.96 GB, 528 Files, 77 Folders, where as it reports one of the subfolder size as 108 GB 1,030 Files, 74 Folders.!!! I do know from another software (TreeSize Free) that the actual size of the Main Folder is 574GB and 54,681 Files). This is unacceptable. How come TreeSize can get it right but File Explorer cannot?? I know you are having issues with File explorer, but when will this issue be resolved?
exactly same problem on windows 10... i was exporting several thousands files to disk into a directory like 'C:\tmp\testexport\2018-09-06-1808\7bb55a1d-3421-4880-8ce1-04ceba06012f\dir1' and properties have reported around 1000 files and 122 directories, when in fact there was over 8000 files and 590 directories. When I moved 'dir1' folder one level higher, properties reported correct counts...
i wonder if it's really the time to give linux a shot one more time... : )
p.s. as i am posting this, i am getting "Unexpected error" when i press submit.. omg omg omg////
Used PathLengthChecker and discovered a photo named with a 22 word sentence created a path length of 271. The second longest path in this directory was 241. With this photo within the Parent directory, Windows properties reported the parent folder contained 44,743 files & 4813 folders occupying 13.3 GB.
Using the Everything search app, I could see there were 164,633 objects (files & folders). I removed the photo from the directory and repeated the Windows properties query. Windows now reported 151,879 files & 12,753 folders totalling 164,632 (one less than that reported by Everything) and occupying 64.4 GB of drive space.
Seems removing the long file path solved the issue; returning it to the directory tree resulted in only 44,743 files reported in Windows properties. Window 10 Pro 64-bit build 1803.
Just an FYI
Have been having these same issues since everyone else has, way back in May + -.
Just noticed that issue is resolved on one of my computers 100%, all property numbers are back to normal on all folders, this just happened since my last back up last week.
My other computer (#2) still has the issue. Thought it might have been the last Windows update but did that update on #2 and no resolve...
Go figure???
Just to add that I'm seeing incorrect no. of files and size of folder using 'Properties' in Windows version 1809
now as well. I'll report this on the Feedback Hub.
Thanks,
Dave.
YES, this is a problem, but I did not realize how serious until you explained "Scenario 1".
Yikes, now I am worried. How can MS not fix this yet?
Same problem here. The guess that it's due to path length is consistent with my experience.
I am trying to sync folders across multiple computers and I spent two days thinking the sync was not working. My original folder has 4 GB of data but the synced folder only reports 800 MB.
The original folder is a root directory in my F drive
The synced folder is nested in Documents.
Without a third party app like TreeSize I'd have no idea if my files were being properly backed up. This is really terrible coding from Microsoft. An unacceptable bug. Managing files is the heart of what an OS is for.
Same problem here
properties display 9 890 files 909 dirs 20.7 Go
simple python prog 2 422 661 files 76 788 dirs 882.7 Go
robocopy 2 422 657 files 76 789 dirs 878.952 Go- Edited by manu9257 Friday, December 21, 2018 1:34 AM
THANKS. IT'S TAKEN A WHILE, BUT THAT IS REALLY GOOD NEWS!
I noticed that I have a July 30, 2017 file backup performed using Windows Explorer file copy (drag and drop) whose properties also display the same type of incorrect information (smaller size, number of files, and number of folders). This would indicate to me that the issue may have existed in versions earlier than 1803.
Ok, Bill, time to get back to coding. Remember how fun it was staying up all night? Forget all that humanitarian stuff for now.
Jack Ritter
www.houseofwords.com
Yesterday I just picked up and installed the re-released 1809 Feature Update (Build 17763). Just taking a shot to see if it might have addressed the current Properties information problem. Unfortunately no, the reported Properties information is still bad related to the cases that have been reported by many people besides myself.
So, as indicated in my previous update from December, according to Microsoft support this will be fixed with the upcoming 18298+ build. From what I see in currently published information, that build level will be associated with the planned 1903 Feature Update.
Bottom line here is that we are still waiting for a formal fix to this problem that was induced by the 1803 Feature Update from Spring of last year.
I am on Version 10.0.171134
My File Explorer Count is Incorrect with Windows 10 Pro
Windows 10 Pro Says 173K + Files the Real count is 209K +
The way that I have Confirmed this
Server 2012R2 Counts the Files as 209K + Down to The File
Qnap File Station counts The files as 209k + Down to the file
Windows 7 Pro Counts the Files As 209K + Down to the file
I thought I had been hacked or sometime bad. MS get your act together
I can only Conclude Windows 10 Pro is the problems
If you want to Count your files try what I did.
Anyone please respond to my request
Thanks
The problem still exists as of today. I bought a new Western Digital 4TB My Passport HD recently. I created a new folder named "Backup1" inside it.
After I transfer files from my old WD 4TB My Book HD, to the new Passport HD, I noticed when I view the properties of the "Backup1" folder, several thousand files were not counted, as compared to my old Book HD.
I thought I had a faulty new HD, ran the WinMerge program, that compare the number of files between the new & old HD, it says both are identical. Luckily I found this forum thread, learned the problem was there were too many subfolders. After I proceed to move my copied files & folders out of "Backup1" folder, the files were once again counted correctly. I wonder when is this bug going to get fixed.
Today, after updating Windows 10 Pro from version 1803 to version 1903, File Explorer now seems to correctly count folders and files (and their sizes).
Apparently fixed on my computer is a problem where File Explorer had been incorrectly reporting properties of folders that had been backed up from internal hard disk drive to external portable disk.
Thanks, Microsoft.
- Proposed as answer by EckiS Wednesday, June 12, 2019 7:35 PM
This problem is DEFINITELY not fixed.
I'm on build 18363 and it is still a problem.
I have a network share to another windows 10 machine.
- "Properties" as reported by the local system from which the share is exported <build 18363> shows: 43,864 Files, 3,378 Folders
- "Properties" as reported by the remote system accessing the exported share <also build 18363> shows: 16 Files, 3,378 Folders
Independent verification using "WinDirStat" (utility application) reports: 43,305 Files, 3,378 Folders.
I can account for WinDirStat's discrepancy by exclusion of hidden/system files.
This appears to be written by the same person that does the windows file copy time estimation dialog.
- Edited by SteveZ1 Saturday, February 22, 2020 9:48 PM
No comments:
Post a Comment