SOLVED
Home

Known Folder Move fails, error code 0x80004005

%3CLINGO-SUB%20id%3D%22lingo-sub-214911%22%20slang%3D%22en-US%22%3EKnown%20Folder%20Move%20fails%2C%20error%20code%200x80004005%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-214911%22%20slang%3D%22en-US%22%3E%3CP%3EI%20have%20enabled%20the%20group%20policy%20setting%20to%20prompt%20users%26nbsp%3Bto%20move%20known%20folders%20to%20onedrive.%26nbsp%3B%20On%20my%20workstation%2C%20I%20am%20now%20receiving%20the%20prompt%2C%20but%20when%20I%20click%20the%20start%20protection%20button%20it%20fails.%26nbsp%3B%20The%20error%20code%20returned%20is%200x80004005.%26nbsp%3BI've%20been%20searching%20for%20any%20logs%20from%20Onedrive%20which%20might%20provide%20more%20detail%20as%20to%20why%20it%20failed%2C%20but%20haven't%20turned%20anything%20up%20yet.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20could%20cause%20this%20to%20fail%3F%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-center%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F37544iC835579C2650C5BE%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22OD4BError.png%22%20title%3D%22OD4BError.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBackground%20-%20I%20previously%20had%20redirected%20known%20folders%20to%20OneDrive%20using%20the%20old%20method.%26nbsp%3B%20I%20did%20not%20see%20the%20prompt%20to%20protect%20known%20folders%20initially%20when%20I%20got%20the%20new%20OneDrive%20version.%26nbsp%3B%20I%20turned%20off%20the%20old%20folder%20redirection%20policy%20and%20logged%20off%2Fon%20a%20couple%20of%20times%20to%20allow%20it%20to%20redirect%20my%20folders%20back%20to%20the%20original%20location.%26nbsp%3B%20After%20that%2C%26nbsp%3Bthe%20prompt%20to%20protect%20my%20folders%20appeared.%26nbsp%3B%20It's%20possible%20that%20some%20old%20bit%20of%20configuration%20is%20causing%20the%20Known%20Folder%20Move%20to%20fail.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-214911%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EFiles%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOneDrive%20for%20Business%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-280842%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Folder%20Move%20fails%2C%20error%20code%200x80004005%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-280842%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20thrilled%20to%20report%20that%20OneDrive%20support%20contacted%20me%20today%20and%20my%20issue%20has%20been%20resolved.%26nbsp%3B%20Unfortunately%2C%20the%20root%20cause%20in%20my%20case%20may%20be%20completely%20different%26nbsp%3Bothers%2C%20but%20I%20want%20to%20share%20it%20here%20anyway%20just%20in%20case%20it%20might%20be%20of%20help%20to%20someone.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAs%20I%20mentioned%20previously%2C%20OneDrive%20support%20had%20identified%20and%20removed%20a%20second%20OneDrive%20for%20Business%20library%20related%20to%20my%20account%2C%20which%20had%20a%201%20appended%20to%20the%20end%20of%20the%20UPN.%26nbsp%3B%20As%20it%20turns%20out%2C%20there%20was%20actually%20a%203rd%20OneDrive%20for%20Business%20library%20for%20my%20account%2C%20this%20one%20using%20a%20UPN%20with%20our%20'domain.onmicrosoft.com'%20domain%20instead%20of%20our%20primary%20domains.%20%26nbsp%3BIt%20seems%20that%20the%202%20accounts%20were%20somehow%20conflicting%20when%20KFM%20tried%20to%20turn%20on%2C%20and%20causing%20it%20to%20fail.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%2C%20even%20if%20they've%20already%20looked%20into%20a%20possible%20second%20library%20for%20an%20account%20having%20issues%2C%20it%20might%20be%20worth%20having%20them%20look%20again%2C%20this%20time%20for%20one%20using%20an%20onmicrosoft.com%20domain%20or%20alternate%20domain%20associated%20with%20your%20tenant.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20hope%20that%20helps!%3C%2FP%3E%3CP%3ESteve%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-269890%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Folder%20Move%20fails%2C%20error%20code%200x80004005%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-269890%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20a%20quick%20update%20to%20say%20that%20I've%20still%20made%20no%20progress%20here.%26nbsp%3B%20Support%20has%20tried%20a%20few%20more%20things%2C%20to%20no%20avail.%26nbsp%3B%20One%20thing%20they%20tried%20a%20few%20weeks%20ago%20is%20worth%20noting%20-%3C%2FP%3E%3CP%3ELike%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F177791%22%20target%3D%22_blank%22%3E%40Chris%20Grist%3C%2FA%3E%2C%20I%20apparently%20had%202%20OneDrive%20for%20Business%20libraries.%26nbsp%3B%20When%20I%20opened%20my%20OneDrive%20for%20business%20library%20in%20a%20web%20browser%2C%20the%20URL%20included%20my%20email%20address%20with%20a%20'1'%20appended%20to%20the%20end%20of%20it.%26nbsp%3B%20If%20I%20modified%20the%20URL%2C%20removing%20the%201%20from%20the%20end%20of%20my%20email%20address%2C%20it%20took%20me%20to%20the%20empty%20library.%26nbsp%3B%3C%2FP%3E%3CP%3EInitially%2C%20support%20was%20going%20to%20delete%20the%20empty%20library%20and%20rename%20the%20one%20containing%20my%20data%20to%20remove%20the%20'1'%2C%20but%20they%20were%20not%20able%20to%20do%20that%20for%20some%20reason.%26nbsp%3B%20Instead%2C%20they%20had%20me%20turn%20off%20Files%20on%20Demand%20and%20sync%20my%20entire%20onedrive%20library%20to%20My%20PC%2C%20then%20unlink%20my%20onedrive%20client%20from%20my%20account.%26nbsp%3B%20Then%20they%20deleted%20the%20library%20with%20the%20'1'%20attached%2C%20and%20updated%20my%20account%20to%20point%20to%20the%20empty%20library%2C%20without%20the%20'1'.%26nbsp%3B%20Then%20I%20signed%20back%20in%20to%20OneDrive%20on%20my%20PC%2C%20linking%20my%20account%20to%20the%20client%2C%20and%20it%20uploaded%20all%20of%20my%20data%20into%20that%20library.%26nbsp%3B%3C%2FP%3E%3CP%3EOne%20important%20note%20here%20--%20Despite%26nbsp%3Bassurances%20from%20the%20support%20rep%20that%20this%20process%20would%20serve%20to%20backup%20and%20restore%20all%20of%20my%20data%2C%20that%20was%20not%20the%20case.%26nbsp%3B%20%3CSTRONG%3EThis%20process%20caused%20data%20loss.%3C%2FSTRONG%3E%26nbsp%3B%20It%20turns%20out%20that%26nbsp%3BOneNote%20notebooks%20are%20stored%20in%20OneDrive%2C%20but%20managed%20by%20OneNote%2C%20and%20the%20OneDrive%20client%20does%20not%20synchronize%20those%20files%2Ffolders.%26nbsp%3B%20I%20lost%20multiple%20OneNote%20notebooks%20because%20of%20this.%26nbsp%3B%20Fortunately%2C%20the%20most%20important%20and%20frequently%20used%20notebook%20was%20cached%20by%20OneNote%20on%20my%20PC%2C%20and%20I%20was%20able%20to%20copy%20and%20paste%20every%20note%20from%20it%20into%20a%20new%20notebook.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDeleting%20the%20extra%20library%20did%20not%20fix%20my%20issue%20with%20Known%20Folder%20Move.%26nbsp%3B%20Support%20has%20had%20me%20try%20a%20couple%20of%20other%20things%20since%20then%2C%20but%20nothing%20has%20helped.%26nbsp%3B%20Most%20recently%2C%20they%20asked%20me%20to%20reproduce%20the%20issue%20and%20send%20them%20the%20client%20logs%20again%20for%20further%20review.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUgh.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-269873%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Folder%20Move%20fails%2C%20error%20code%200x80004005%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-269873%22%20slang%3D%22en-US%22%3E%3CP%3EI've%20found%20that%20if%20you%20have%20an%20Group%20Policies%20in%20place%20relating%20to%20Folder%20Redirection%2C%20you%20need%20to%20get%20rid%20of%20them.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3EI%20haven't%20tested%20fully%2C%20but%20it%20was%20due%20to%20an%20existing%20policy.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-267805%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Folder%20Move%20fails%2C%20error%20code%200x80004005%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-267805%22%20slang%3D%22en-US%22%3E%3CP%3EI%20found%20out%20I%20had%20two%20onedrive%20sites.%20deleted%20both%20and%20created%20a%20fresh%20one%20and%20still%20no%20better!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-266538%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Folder%20Move%20fails%2C%20error%20code%200x80004005%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-266538%22%20slang%3D%22en-US%22%3EI%20have%20the%20same%20issue%20and%20have%20confirmed%20it%20appears%20to%20be%20account%20specific%20as%20new%20accounts%20have%20been%20OK.%20Not%20found%20a%20fix%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-260633%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Folder%20Move%20fails%2C%20error%20code%200x80004005%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-260633%22%20slang%3D%22en-US%22%3E%3CP%3EHave%20been%20having%20the%20same%20issue%20for%20weeks%20and%20weeks.%3C%2FP%3E%3CP%3EIt's%20(probably)%20account%20specific%2C%20but%20there%20are%20many%20reasons%20why%20it%20might%20not%20work%2C%20eg%20if%20your%20profile%20folders%20are%20redirecting%20to%20another%20volume%20than%20the%20one%20OneDrive%20is%20residing%20on%2C%20it%20will%20not%20work.%3C%2FP%3E%3CP%3EAfter%20correcting%20some%20of%20those%20documented%20prerequisites%2C%20it%20still%20doesn't%20work.%3C%2FP%3E%3CP%3EAlso%3A%20my%20work%20style%20is%20completely%20nomadic%20so%20I%20log%20in%20and%20out%20of%20a%20lot%20of%20machines%20on%20a%20daily%2Fweekly%20basis%20(AD%20joined%2C%20Azure%20joined%2C%20workgroup%20joined)%20-%20I%20suspect%20that%20if%20one%20of%20those%20machines%20has%20an%20issue%20preventing%20KFM%2C%20it%20probably%20blocks%20the%20feature%20working%20anywhere.%20Would%20be%20horrible%20architectural%20design%20but%20I%20would%20not%20be%20surprised.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EConclusion%3A%20sadly%20another%20MS%20feature%20that%20is%20not%20tested%2C%20half%20baked%20and%20not%20thought%20through.%3C%2FP%3E%3CP%3EWhich%20is%20a%20pity%20because%20it's%20a%20good%20idea%3A%20makes%20your%20profile%20data%20more%20available%2C%20potentially%20protects%20against%20ransomware%20etc%20%3D%26gt%3B%20finally%20an%20area%20where%20MS%20could%20make%20a%20difference...%20alas.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-239602%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Folder%20Move%20fails%2C%20error%20code%200x80004005%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-239602%22%20slang%3D%22en-US%22%3EAnd%2C%20FWIW%2C%20I%20did%20build%20a%20fresh%20VM%20with%20Win10%20installed%20from%20media%2C%20log%20in%20with%20a%20new%20local%20account%2C%20and%20sign%20into%20OneDrive%20with%20my%20O365%20account.%20Even%20then%2C%20I%20get%20the%20same%20error%20when%20trying%20to%20enable%20Known%20Folder%20Move.%20So%2C%20definitely%20not%20an%20issue%20with%20the%20client%20pc%20or%20environment%20specific%20policies%20etc.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-239502%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Folder%20Move%20fails%2C%20error%20code%200x80004005%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-239502%22%20slang%3D%22en-US%22%3E%3CDIV%3E%3CBR%20%2F%3EHere%20are%20a%20few%20more%20details%20about%20my%20issue%20that%20I've%20found%20since%20I%20posted%20originally%3A%3C%2FDIV%3E%3CDIV%3EMy%20issue%20definitely%20seems%20to%20be%20account%20specific.%26nbsp%3B%20I've%20enabled%20KFM%20for%20many%20other%20users%20in%20our%20org%20at%20this%20point%2C%20and%20no%20other%20users%20get%20this%20error.%26nbsp%3B%20For%20me%2C%20I've%20tried%20across%20multiple%20computers%2C%20including%20freshly%20imaged%20computers.%26nbsp%3B%20The%20version%20of%20OneDrive%20client%20doesn't%20make%20a%20difference%20either.%26nbsp%3B%20It's%20been%20happening%20since%20the%20first%20KFM%20enabled%20version%20came%20down%2C%20and%20continues%20still%20in%20the%20current%20versions.%26nbsp%3B%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EThe%20one%20thing%20I%20guess%20I%20haven't%20tried%20yet%20is%20a%20clean%20install%20of%20Win%2010%20direct%20from%20media%2C%20not%20domain%20joined.%26nbsp%3B%20I%20don't%20expect%20that%20to%20make%20a%20difference%2C%20but%20I'll%20spin%20up%20a%20VM%20today%20and%20try%20it.%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3EI've%20had%20a%20ticket%20open%20with%20OneDrive%20support%20since%20mid%20July%2C%20and%20after%20initial%20activity%20going%20back%20and%20forth%20with%20the%20support%20rep%2C%20remote%20sessions%20to%20demonstrate%20the%20issue%20to%20him%2C%20collecting%20and%20sharing%20log%20files%2C%20trying%20different%20client%20versions%2C%20different%20computers%2C%20etc%2C%20I%20was%20told%20that%20the%20ticket%20was%20being%20passed%20to%20their%20escalation%20team.%26nbsp%3B%20Since%20then%2C%20there%20has%20been%20zero%20activity%20other%20than%20replying%20to%20my%20request%20for%20updates%20to%20tell%20me%20that%20it's%20with%20the%20escalation%20team%20and%20there%20is%20nothing%20more%20to%20be%20done%20until%20that%20team%20responds.%26nbsp%3B%20(Ticket%20%23687064%2C%20in%20case%20anyone%20from%20MS%20is%20reading%20and%20wants%20to%20look%20into%20it.)%3C%2FDIV%3E%3CDIV%3E%26nbsp%3B%3C%2FDIV%3E%3CDIV%3ESo%2C%20I%20guess%20the%20tl%2Cdr%20for%20this%20update%20is%20that%20there%20is%20no%20update.%26nbsp%3B%20Just%20more%20detail.%20%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-239443%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Folder%20Move%20fails%2C%20error%20code%200x80004005%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-239443%22%20slang%3D%22en-US%22%3EI've%20been%20through%20multiple%20versions%20at%20this%20point%2C%20OneDrive%20updates%20to%20new%20versions%2C%20but%20the%20issue%20continues.%20Currently%2C%20on%20my%20primary%20computer%20I%20am%20running%20build%2018.162.0812.0001.%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-239048%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Folder%20Move%20fails%2C%20error%20code%200x80004005%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-239048%22%20slang%3D%22en-US%22%3EI%20am%20also%20facing%20the%20same%20issue%20when%20enabling%20this%20setting%20via%20GPO.%20Could%20you%20please%20tell%20me%20the%20version%20of%20sync%20client%20which%20you%20are%20using%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-238028%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Folder%20Move%20fails%2C%20error%20code%200x80004005%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-238028%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F181268%22%20target%3D%22_blank%22%3E%40Jitin%20Sadana%3C%2FA%3ECan%20you%20elaborate%20a%20little%20more%20on%20your%20fix%3F%26nbsp%3B%20How%20did%20you%20find%20that%20the%20sync%20client%20is%20not%20updating%20the%20folder%20locations%3F%26nbsp%3B%20Where%20did%20you%20manually%20change%20this%20to%20resolve%20the%20issue%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESteve%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-238018%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Folder%20Move%20fails%2C%20error%20code%200x80004005%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-238018%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F181268%22%20target%3D%22_blank%22%3E%40Jitin%20Sadana%3C%2FA%3EUnfortunately%2C%20there%20has%20been%20no%20progress.%26nbsp%3B%20A%20few%20weeks%20ago%2C%20my%20support%20ticket%20was%20passed%20to%20an%20escalation%20team%2C%20and%20I%20have%20not%20heard%20a%20thing%20from%20them%20since.%26nbsp%3B%20I've%20emailed%20to%20request%20a%20status%20update%20each%20week%2C%20but%26nbsp%3Bthe%20support%20rep%20simply%20re-iterates%20that%20my%20ticket%20was%20passed%20to%20the%20escalation%20team%2C%20and%20when%20they%20give%20him%20an%20update%20he%20will%20let%20me%20know.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20far%2C%20the%20escalation%20team%20seems%20to%20be%20something%20of%20a%20black%20hole%2C%20which%20a%20ticket%20goes%20in%20to%20but%20nothing%20ever%20comes%20out%20of.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-238012%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Folder%20Move%20fails%2C%20error%20code%200x80004005%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-238012%22%20slang%3D%22en-US%22%3E%3CP%3EManually%20moving%20isn't%20the%20best%20option%20for%20us%20as%20we%20want%20to%20roll%20it%20out%20without%20having%20to%20touch%20the%20devices.%26nbsp%3B%20I%20haven't%20had%20chance%20to%20test%20it%20again.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20might%20give%20it%20a%20few%20more%20weeks%20and%20hope%20all%20the%20bugs%20are%20ironed%20out.%26nbsp%3B%20I%20want%20to%20roll%20it%20out%20via%20GPO.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-237913%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Folder%20Move%20fails%2C%20error%20code%200x80004005%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-237913%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20I%20found%20the%20fix%20of%20this%20issue.%20This%20is%20an%20issue%20as%20sync%20client%20is%20not%20updating%20the%20location%20of%20the%20known%20folders.%20You%20can%20manually%20update%20the%20location%20which%20will%20resolve%20the%20issue.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-237839%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Folder%20Move%20fails%2C%20error%20code%200x80004005%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-237839%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20update%20on%20this%20issue%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-227859%22%20slang%3D%22en-US%22%3ERe%3A%20Known%20Folder%20Move%20fails%2C%20error%20code%200x80004005%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-227859%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Steve%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI've%20ran%20into%20this%20exact%20issue%20on%20my%20first%20test%20laptop%20when%20the%20KFM%20feature%20appeared.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20you%20got%20any%20where%20with%20the%20problem%3F%26nbsp%3B%20I%20haven't%20had%20time%20to%20look%20into%20it%20any%20future%20but%20am%20not%20hoping%20to%20have%20a%20closer%20look%20this%20week%20some%20time.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3CP%3EStephen.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Steve Whitcher
Regular Contributor

I have enabled the group policy setting to prompt users to move known folders to onedrive.  On my workstation, I am now receiving the prompt, but when I click the start protection button it fails.  The error code returned is 0x80004005. I've been searching for any logs from Onedrive which might provide more detail as to why it failed, but haven't turned anything up yet. 

 

What could cause this to fail?

OD4BError.png

 

 

 

Background - I previously had redirected known folders to OneDrive using the old method.  I did not see the prompt to protect known folders initially when I got the new OneDrive version.  I turned off the old folder redirection policy and logged off/on a couple of times to allow it to redirect my folders back to the original location.  After that, the prompt to protect my folders appeared.  It's possible that some old bit of configuration is causing the Known Folder Move to fail.  

16 Replies

Hi Steve,

 

I've ran into this exact issue on my first test laptop when the KFM feature appeared.  

 

Have you got any where with the problem?  I haven't had time to look into it any future but am not hoping to have a closer look this week some time.  

 

Thanks!

Stephen.

Any update on this issue ?

Hey I found the fix of this issue. This is an issue as sync client is not updating the location of the known folders. You can manually update the location which will resolve the issue.

Manually moving isn't the best option for us as we want to roll it out without having to touch the devices.  I haven't had chance to test it again.  

 

I might give it a few more weeks and hope all the bugs are ironed out.  I want to roll it out via GPO.

@Jitin SadanaUnfortunately, there has been no progress.  A few weeks ago, my support ticket was passed to an escalation team, and I have not heard a thing from them since.  I've emailed to request a status update each week, but the support rep simply re-iterates that my ticket was passed to the escalation team, and when they give him an update he will let me know.  

 

So far, the escalation team seems to be something of a black hole, which a ticket goes in to but nothing ever comes out of.  

@Jitin SadanaCan you elaborate a little more on your fix?  How did you find that the sync client is not updating the folder locations?  Where did you manually change this to resolve the issue?

 

Steve

I am also facing the same issue when enabling this setting via GPO. Could you please tell me the version of sync client which you are using?
I've been through multiple versions at this point, OneDrive updates to new versions, but the issue continues. Currently, on my primary computer I am running build 18.162.0812.0001.


Here are a few more details about my issue that I've found since I posted originally:
My issue definitely seems to be account specific.  I've enabled KFM for many other users in our org at this point, and no other users get this error.  For me, I've tried across multiple computers, including freshly imaged computers.  The version of OneDrive client doesn't make a difference either.  It's been happening since the first KFM enabled version came down, and continues still in the current versions. 
 
The one thing I guess I haven't tried yet is a clean install of Win 10 direct from media, not domain joined.  I don't expect that to make a difference, but I'll spin up a VM today and try it.
 
I've had a ticket open with OneDrive support since mid July, and after initial activity going back and forth with the support rep, remote sessions to demonstrate the issue to him, collecting and sharing log files, trying different client versions, different computers, etc, I was told that the ticket was being passed to their escalation team.  Since then, there has been zero activity other than replying to my request for updates to tell me that it's with the escalation team and there is nothing more to be done until that team responds.  (Ticket #687064, in case anyone from MS is reading and wants to look into it.)
 
So, I guess the tl,dr for this update is that there is no update.  Just more detail.  
And, FWIW, I did build a fresh VM with Win10 installed from media, log in with a new local account, and sign into OneDrive with my O365 account. Even then, I get the same error when trying to enable Known Folder Move. So, definitely not an issue with the client pc or environment specific policies etc.

Have been having the same issue for weeks and weeks.

It's (probably) account specific, but there are many reasons why it might not work, eg if your profile folders are redirecting to another volume than the one OneDrive is residing on, it will not work.

After correcting some of those documented prerequisites, it still doesn't work.

Also: my work style is completely nomadic so I log in and out of a lot of machines on a daily/weekly basis (AD joined, Azure joined, workgroup joined) - I suspect that if one of those machines has an issue preventing KFM, it probably blocks the feature working anywhere. Would be horrible architectural design but I would not be surprised.

 

Conclusion: sadly another MS feature that is not tested, half baked and not thought through.

Which is a pity because it's a good idea: makes your profile data more available, potentially protects against ransomware etc => finally an area where MS could make a difference... alas.

I have the same issue and have confirmed it appears to be account specific as new accounts have been OK. Not found a fix

I found out I had two onedrive sites. deleted both and created a fresh one and still no better!

I've found that if you have an Group Policies in place relating to Folder Redirection, you need to get rid of them.  

I haven't tested fully, but it was due to an existing policy.

Just a quick update to say that I've still made no progress here.  Support has tried a few more things, to no avail.  One thing they tried a few weeks ago is worth noting -

Like @Deleted, I apparently had 2 OneDrive for Business libraries.  When I opened my OneDrive for business library in a web browser, the URL included my email address with a '1' appended to the end of it.  If I modified the URL, removing the 1 from the end of my email address, it took me to the empty library. 

Initially, support was going to delete the empty library and rename the one containing my data to remove the '1', but they were not able to do that for some reason.  Instead, they had me turn off Files on Demand and sync my entire onedrive library to My PC, then unlink my onedrive client from my account.  Then they deleted the library with the '1' attached, and updated my account to point to the empty library, without the '1'.  Then I signed back in to OneDrive on my PC, linking my account to the client, and it uploaded all of my data into that library. 

One important note here -- Despite assurances from the support rep that this process would serve to backup and restore all of my data, that was not the case.  This process caused data loss.  It turns out that OneNote notebooks are stored in OneDrive, but managed by OneNote, and the OneDrive client does not synchronize those files/folders.  I lost multiple OneNote notebooks because of this.  Fortunately, the most important and frequently used notebook was cached by OneNote on my PC, and I was able to copy and paste every note from it into a new notebook.  

 

Deleting the extra library did not fix my issue with Known Folder Move.  Support has had me try a couple of other things since then, but nothing has helped.  Most recently, they asked me to reproduce the issue and send them the client logs again for further review.  

 

Ugh.  

Solution

I am thrilled to report that OneDrive support contacted me today and my issue has been resolved.  Unfortunately, the root cause in my case may be completely different others, but I want to share it here anyway just in case it might be of help to someone.

 

As I mentioned previously, OneDrive support had identified and removed a second OneDrive for Business library related to my account, which had a 1 appended to the end of the UPN.  As it turns out, there was actually a 3rd OneDrive for Business library for my account, this one using a UPN with our 'domain.onmicrosoft.com' domain instead of our primary domains.  It seems that the 2 accounts were somehow conflicting when KFM tried to turn on, and causing it to fail. 

 

So, even if they've already looked into a possible second library for an account having issues, it might be worth having them look again, this time for one using an onmicrosoft.com domain or alternate domain associated with your tenant.  

 

I hope that helps!

Steve

Related Conversations
How to Prevent Teams from Auto-Launch
chenrylee in Microsoft Teams on
28 Replies
Tabs and Dark Mode
cjc2112 in Discussions on
2 Replies
*Updated 9/3* Syncing in Microsoft Edge Preview Channels
Elliot Kirk in Articles on
205 Replies
Early preview of Microsoft Edge group policies
Sean Lyndersay in Discussions on
65 Replies