SP2019 Server Quick Launch Nav missing on Modern sites after Aug CU patch install

%3CLINGO-SUB%20id%3D%22lingo-sub-1710029%22%20slang%3D%22en-US%22%3ESP2019%20Server%20Quick%20Launch%20Nav%20missing%20on%20Modern%20sites%20after%20Aug%20CU%20patch%20install%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1710029%22%20slang%3D%22en-US%22%3E%3CP%20data-unlink%3D%22true%22%3EInstalled%20%3CA%20title%3D%22Aug%202020%20CU%22%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4484472%2Fsecurity-update-for-sharepoint-server-2019-august-11-2020%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3EKB4484472%3C%2FA%3E%20yesterday%20on%20SP2019%20Server.%26nbsp%3B%20Users%20today%20started%20to%20complain%20that%20the%20Quick%20Launch%20navigation%20on%20Modern%20sites%20is%20no%20longer%20visible.%26nbsp%3B%20Is%20anyone%20else%20experiencing%20the%20same%20issue%20and%20have%20you%20been%20able%20to%20resolve%20the%20issue%3F%26nbsp%3B%20It%20appears%20that%20Chrome%20and%20IE%20browsers%20are%20only%20affected.%26nbsp%3B%20Using%20Edge%20browser%20seems%20to%20display%20the%20navigation.%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3EThis%20is%20the%20expected%20look%3A%3C%2FP%3E%3CDIV%20class%3D%22mceNonEditable%20lia-copypaste-placeholder%22%3E%26nbsp%3B%3C%2FDIV%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22QuickLaunchNav-Expected.png%22%20style%3D%22width%3A%20661px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F221911iC55EA70F0475BBFE%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22QuickLaunchNav-Expected.png%22%20alt%3D%22QuickLaunchNav-Expected.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EThis%20is%20the%20current%20look%3A%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22QuickLaunchNav-Missing.png%22%20style%3D%22width%3A%20683px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F221912i26B48D259355AAE2%2Fimage-size%2Flarge%3Fv%3D1.0%26amp%3Bpx%3D999%22%20title%3D%22QuickLaunchNav-Missing.png%22%20alt%3D%22QuickLaunchNav-Missing.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance%20for%20any%20insight%20into%20this%20matter.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1710029%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ESharePoint%20Server%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1710665%22%20slang%3D%22en-US%22%3ERe%3A%20SP2019%20Server%20Quick%20Launch%20Nav%20missing%20on%20Modern%20sites%20after%20Aug%20CU%20patch%20install%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1710665%22%20slang%3D%22en-US%22%3EI%20believe%20I%20have%20read%20somewhere%20there%20was%20a%20problem%20with%20the%20CU%20released%20in%20September%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1773427%22%20slang%3D%22en-US%22%3ERe%3A%20SP2019%20Server%20Quick%20Launch%20Nav%20missing%20on%20Modern%20sites%20after%20Aug%20CU%20patch%20install%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1773427%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F99122%22%20target%3D%22_blank%22%3E%40David%20Graham%3C%2FA%3E%26nbsp%3BHi%2C%20we're%20also%20experiencing%20this%20issue.%26nbsp%3B%20Does%20anyone%20know%20if%20this%20gets%20resolved%20in%20the%20Sep%20update%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1843497%22%20slang%3D%22en-US%22%3ERe%3A%20SP2019%20Server%20Quick%20Launch%20Nav%20missing%20on%20Modern%20sites%20after%20Aug%20CU%20patch%20install%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1843497%22%20slang%3D%22en-US%22%3EI%20have%20same%20issue%20after%20installing%20KB4486676.%20Anyone%20have%20solution%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1889734%22%20slang%3D%22en-US%22%3ERe%3A%20SP2019%20Server%20Quick%20Launch%20Nav%20missing%20on%20Modern%20sites%20after%20Aug%20CU%20patch%20install%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1889734%22%20slang%3D%22en-US%22%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHello%2C%3C%2FP%3E%3CP%3EI%20have%20the%20same%20issue%20with%20our%20SharePoint%202019%20environment%20after%20installing%20kb4486676%20October%20CU.%3C%2FP%3E%3CP%3EAnyone%20else%20found%20a%20solution%3F%20Our%20workaround%20is%20to%20change%20the%20default%20navigation%20from%20Home.aspx%20to%20Documents.aspx%3C%2FP%3E%3CP%3EThis%20affected%20the%20whole%20farm%20(thousands%20of%20sites)%3C%2FP%3E%3CP%3EI%20found%20others%20with%20similar%20issues%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fanswers%2Fquestions%2F80671%2Fshareppoint-2019-modern-team-site-template-issue.html%3FchildToView%3D163899%23answer-163899%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-us%2Fanswers%2Fquestions%2F80671%2Fshareppoint-2019-modern-team-site-template-issue.html%3FchildToView%3D163899%23answer-%3C%2FA%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fsharepoint%2Fsp2019-server-quick-launch-nav-missing-on-modern-sites-after-aug%2Fm-p%2F1710029%22%20target%3D%22_blank%22%3E163899https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fsharepoint%2Fsp2019-server-quick-launch-nav-missing-on-modern-sites-after-aug%2Fm-p%2F1710029%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3Ebut%20no%20solution%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1892927%22%20slang%3D%22en-US%22%3ERe%3A%20SP2019%20Server%20Quick%20Launch%20Nav%20missing%20on%20Modern%20sites%20after%20Aug%20CU%20patch%20install%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1892927%22%20slang%3D%22en-US%22%3E%3CP%3EMissing%20left%20navigation%20in%203%20consecutive%20patches.%26nbsp%3B%20You%20would%20think%20MS%20devs%20and%20testers%20would%20have%20noticed%20this%20by%20now.%26nbsp%3B%20Real%20slack%20units.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20anyone%20confirm%20if%20the%20Nov%20patch%20fixes%20this%20%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1921576%22%20slang%3D%22en-US%22%3ERe%3A%20SP2019%20Server%20Quick%20Launch%20Nav%20missing%20on%20Modern%20sites%20after%20Aug%20CU%20patch%20install%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1921576%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F262243%22%20target%3D%22_blank%22%3E%40nick_trinidad%3C%2FA%3E%26nbsp%3BAfter%20opening%20a%20case%20with%20MS%2C%20they%20recommended%20instsalling%20the%20following%20KB%3C%2FP%3E%3CP%3E%3CSPAN%3E%26nbsp%3B(KB4486675)%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%20%26lt%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4486675%2Foctober-13-2020-update-for-sharepoint-server-2019-language-pack-kb4486%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4486675%2Foctober-13-2020-update-for-sharepoint-server-2019-language-pack-kb4486%3C%2FA%3E%26gt%3B%3C%2FP%3E%3CP%3EIt%20resolved%20the%20issue%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1931774%22%20slang%3D%22en-US%22%3ERe%3A%20SP2019%20Server%20Quick%20Launch%20Nav%20missing%20on%20Modern%20sites%20after%20Aug%20CU%20patch%20install%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1931774%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F632532%22%20target%3D%22_blank%22%3E%40MSaeed7%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20did%20not%20work%20or%20us.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20seems%20to%20be%20related%20to%20the%20edit%2Fpublish%20options%20in%20the%20grey%20bar%20that%20goes%20above%20our%20news%20content.%20Every%20single%20site%20page%20with%20edit%2Fpublish%20is%20affected.%20The%20javascript%20is%20a%20mess%20of%20errors%20when%20you%20view%20the%20code%20on%20the%20page.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EOther%20documents%2C%20or%20system%20pages%20show%20the%20modern%20menu%20just%20fine%20but%20this%20is%20not%20how%20sharepoint%20is%20typically%20viewed%20by%20most%20people%20in%20an%20organization.%26nbsp%3B%20We're%20about%202%20seconds%20away%20from%20just%20switching%20to%20dokuwiki%20or%20something%20else.%20This%20has%20been%20weeks.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1951397%22%20slang%3D%22en-US%22%3ERe%3A%20SP2019%20Server%20Quick%20Launch%20Nav%20missing%20on%20Modern%20sites%20after%20Aug%20CU%20patch%20install%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1951397%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20installed%20the%20November%20CU.%20Still%20same%20problem.%20The%20Nav%20is%20available%20on%20Google%20Chrome%20and%20the%20old%20IE11.%3CBR%20%2F%3E%3CBR%20%2F%3EPlease%20Microsoft%26nbsp%3B%20fix%20this%20problem!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1975580%22%20slang%3D%22en-US%22%3ERe%3A%20SP2019%20Server%20Quick%20Launch%20Nav%20missing%20on%20Modern%20sites%20after%20Aug%20CU%20patch%20install%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1975580%22%20slang%3D%22en-US%22%3ESame%20here%20after%20installation%20of%20Dec%20CU.%20Microsoft%20please%20fix%2C%20thanks!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1976618%22%20slang%3D%22en-US%22%3ERe%3A%20SP2019%20Server%20Quick%20Launch%20Nav%20missing%20on%20Modern%20sites%20after%20Aug%20CU%20patch%20install%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1976618%22%20slang%3D%22en-US%22%3E%3CP%3EDecember%20update%20applied.%26nbsp%3B%20No%20fix%20still.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1979390%22%20slang%3D%22en-US%22%3ERe%3A%20SP2019%20Server%20Quick%20Launch%20Nav%20missing%20on%20Modern%20sites%20after%20Aug%20CU%20patch%20install%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1979390%22%20slang%3D%22en-US%22%3E%3CP%3EInstalling%20KB4486675%20did%20the%20trick%20for%20me!%3CBR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D102240%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D102240%3C%2FA%3E%3C%2FP%3E%3CP%3E..%20and%20remember%20PSConfig%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1995760%22%20slang%3D%22en-US%22%3ERe%3A%20SP2019%20Server%20Quick%20Launch%20Nav%20missing%20on%20Modern%20sites%20after%20Aug%20CU%20patch%20install%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1995760%22%20slang%3D%22en-US%22%3E%3CP%20data-unlink%3D%22true%22%3EI%20just%20installed%20a%20new%20SharePoint%202019%20Farm%20with%20the%20Dec%202020%20CU%20using%20the%20AutoSPInstaller.com%20powershell%20installer%20and%20I%20am%20seeing%20the%20same%20thing.%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3EThe%20powershell%20installer%20choked%20and%20I%20had%20to%20setup%20the%20Default%20Site%20from%20the%20SharePoint%20Central%20Administration%20site.%26nbsp%3B%20Any%20site%20I%20create%20has%20the%20same%20issue.%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%3CSPAN%3EInstalling%20KB4486675%20did%20not%20fix%20it.%3C%2FSPAN%3E%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%3CSPAN%3EOddly%20enough%2C%20the%20MySites%20web%20application%20work%20fine.%3C%2FSPAN%3E%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%26nbsp%3B%3C%2FP%3E%3CP%20data-unlink%3D%22true%22%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2023228%22%20slang%3D%22en-US%22%3ERe%3A%20SP2019%20Server%20Quick%20Launch%20Nav%20missing%20on%20Modern%20sites%20after%20Aug%20CU%20patch%20install%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2023228%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F99122%22%20target%3D%22_blank%22%3E%40David%20Graham%3C%2FA%3E%26nbsp%3BWe%20have%20also%20been%20affected%20by%20this%20issue%20for%20months!%20I%20finally%20got%20fed%20up%20and%20did%20some%20sleuthing%20in%20the%20code.%20It%20seems%20that%20the%20sp-pages-assembly.js%20file%20got%20replaced%20by%20a%20newer%20version%20which%20is%20creating%20most%20of%20these%20issues.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20will%20preface%20this%20by%20saying%2C%20always%20make%20backups%20before%20you%20try%20unverified%20solutions%20such%20as%20this%20one.%20I%20did%20such%20by%20copying%20the%20files%20I%20would%20be%20replacing%20in%20a%20backup%20directory%2C%20in%20the%20case%20that%20I%20need%20to%20revert%20back%20later.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20this%20directory%3A%3C%2FP%3E%3CP%3E%3CSTRONG%3EC%3A%5CProgram%20Files%5CCommon%20Files%5Cmicrosoft%20shared%5CWeb%20Server%20Extensions%5C16%5CTEMPLATE%5CLAYOUTS%5CNext%5Cspclient%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThere%20are%20some%20layout%20folders.%20One%20labeled%20'%3CSTRONG%3Edefault%3C%2FSTRONG%3E'%20and%20one%20as%20'%3CSTRONG%3Een-us%3C%2FSTRONG%3E'.%26nbsp%3B%20'%3CSTRONG%3Een-us%3C%2FSTRONG%3E'%20in%20the%20URL%20pointed%20me%20to%20that%20folder%20as%20holding%20the%20offending%20file.%20In%20the%20console%2C%20it%20kept%20saying%20'cannot%20read%20property%20'call'%20of%20undefined'%20stemming%20from%20this%20file%3A%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Friver.nflibrary.ca%2F_layouts%2F15%2Fnext%2Fspclient%2Fen-us%2Fsp-pages-assembly.js%3FuniqueId%3DmadS1%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Friver.nflibrary.ca%2F_layouts%2F15%2Fnext%2Fspclient%2F%3CSTRONG%3Een-us%3C%2FSTRONG%3E%2Fsp-pages-assembly.js%3FuniqueId%3DmadS1%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20I%20replaced%20the%20%3CSTRONG%3Esp-pages-assembly.js%3C%2FSTRONG%3E%20file%20in%20the%20'%3CSTRONG%3Een-us%3C%2FSTRONG%3E'%20folder%20with%20the%20older%20file%20in%20the%20'%3CSTRONG%3Edefaults%3C%2FSTRONG%3E'%20folder.%20(After%20backing%20it%20up)%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAfter%20this%2C%20the%20navigation%20came%20back.%20There%20are%20some%20things%20that%20still%20don't%20look%20right%20as%20labels%20aren't%20being%20updated%20from%20machine%20labels%20for%20example.%20but%20the%20navigation%20is%20back%20and%20we%20can%20edit%20modern%20pages%20again.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20may%20also%20need%20to%20open%20a%20CMD%20as%20Admin%20and%20run%20IIS%20reset%20as%20well%20as%20doing%20a%20hard%20reload%20on%20the%20site%20to%20get%20the%20updates%20to%20appear%20as%20caching%20can%20keep%20you%20from%20seeing%20the%20changes%20until%20then.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt%20seems%20that%20the%20navigation%20missing%20could%20be%20stemming%20from%20an%20issue%20with%20the%20publishing%20bar%20on%20modern%20sites%20as%20the%20navigation%20would%20appear%20again%20if%20I%20was%20in%20a%20list%2C%20that%20uses%20the%20modern%20layout%20but%20has%20a%20list%20bar%20instead%20of%20a%20publishing%20bar.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIt's%20not%20perfect%2C%20but%20it's%20at%20least%20usable%20again.%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Installed KB4484472 yesterday on SP2019 Server.  Users today started to complain that the Quick Launch navigation on Modern sites is no longer visible.  Is anyone else experiencing the same issue and have you been able to resolve the issue?  It appears that Chrome and IE browsers are only affected.  Using Edge browser seems to display the navigation.

This is the expected look:

 

QuickLaunchNav-Expected.png

This is the current look:

QuickLaunchNav-Missing.png

 

Thanks in advance for any insight into this matter.

30 Replies
I believe I have read somewhere there was a problem with the CU released in September

@David Graham Hi, we're also experiencing this issue.  Does anyone know if this gets resolved in the Sep update ?

I have same issue after installing KB4486676. Anyone have solution?

 

Hello,

I have the same issue with our SharePoint 2019 environment after installing kb4486676 October CU.

Anyone else found a solution? Our workaround is to change the default navigation from Home.aspx to Documents.aspx

This affected the whole farm (thousands of sites)

I found others with similar issues

https://docs.microsoft.com/en-us/answers/questions/80671/shareppoint-2019-modern-team-site-template-...163899https://techcommunity.microsoft.com/t5/sharepoint/sp2019-server-quick-launch-nav-missing-on-mo...

 

but no solution

Missing left navigation in 3 consecutive patches.  You would think MS devs and testers would have noticed this by now.  Real slack units.

 

Can anyone confirm if the Nov patch fixes this ?

@nick_trinidad After opening a case with MS, they recommended instsalling the following KB

 (KB4486675)

 

From <https://support.microsoft.com/en-us/help/4486675/october-13-2020-update-for-sharepoint-server-2019-l...>

It resolved the issue

@MSaeed7 

 

This did not work or us.

 

It seems to be related to the edit/publish options in the grey bar that goes above our news content. Every single site page with edit/publish is affected. The javascript is a mess of errors when you view the code on the page. 

 

Other documents, or system pages show the modern menu just fine but this is not how sharepoint is typically viewed by most people in an organization.  We're about 2 seconds away from just switching to dokuwiki or something else. This has been weeks.

 

 

We installed the November CU. Still same problem. The Nav is available on Google Chrome and the old IE11.

Please Microsoft  fix this problem!

Same here after installation of Dec CU. Microsoft please fix, thanks!

December update applied.  No fix still.

Installing KB4486675 did the trick for me!
https://www.microsoft.com/en-us/download/details.aspx?id=102240

.. and remember PSConfig :)

I just installed a new SharePoint 2019 Farm with the Dec 2020 CU using the AutoSPInstaller.com powershell installer and I am seeing the same thing.

The powershell installer choked and I had to setup the Default Site from the SharePoint Central Administration site.  Any site I create has the same issue.

Installing KB4486675 did not fix it.

Oddly enough, the MySites web application work fine.

 

 

@David Graham We have also been affected by this issue for months! I finally got fed up and did some sleuthing in the code. It seems that the sp-pages-assembly.js file got replaced by a newer version which is creating most of these issues. 

 

I will preface this by saying, always make backups before you try unverified solutions such as this one. I did such by copying the files I would be replacing in a backup directory, in the case that I need to revert back later. 

 

In this directory:

C:\Program Files\Common Files\microsoft shared\Web Server Extensions\16\TEMPLATE\LAYOUTS\Next\spclient

 

There are some layout folders. One labeled 'default' and one as 'en-us'.  'en-us' in the URL pointed me to that folder as holding the offending file. In the console, it kept saying 'cannot read property 'call' of undefined' stemming from this file:

https://river.nflibrary.ca/_layouts/15/next/spclient/en-us/sp-pages-assembly.js?uniqueId=madS1

 

So I replaced the sp-pages-assembly.js file in the 'en-us' folder with the older file in the 'defaults' folder. (After backing it up)

 

After this, the navigation came back. There are some things that still don't look right as labels aren't being updated from machine labels for example. but the navigation is back and we can edit modern pages again. 

 

You may also need to open a CMD as Admin and run IIS reset as well as doing a hard reload on the site to get the updates to appear as caching can keep you from seeing the changes until then. 

 

It seems that the navigation missing could be stemming from an issue with the publishing bar on modern sites as the navigation would appear again if I was in a list, that uses the modern layout but has a list bar instead of a publishing bar. 

 

It's not perfect, but it's at least usable again.

Tried replacing the requested JS file but no luck , wondering if there is proper fix from Microsoft , its being couple of months now .

 

Thanks,

Nalin
@cburton228 

@MSaeed7 - Hello everyone, we are facing the same issue too. I installed the latest Dec 2020 KB hoping that would resolve the issue but it didn't. I haven't installed the Oct 2020 KB at all.. Can I install the Oct 2020 KB now? or will this impact the farm ?any help is greatly appreciated.

@dmonnala We had the same problem with the December CU already installed. The solution was probably to apply the October and November patches, which also works when December is installed. It is important that you install the multilingual update for your language and not only the core.

 

So you have to install KB 4486715 instead of KB 4486714.

@dmonnala 

I just applied the january security patch KB4493161. had the same issue until I cleared my browser cache.

Today I tried installing the January 2021 CU on all my SharePoint 2019 Servers and the problem still exits.

It will not let me install the October or November 2020 CU updates.  I'll guess it's because these are Cumulative Updates and you should not need to install anything but the latest update.

@rukueu  Thank you for your response. So the Jan 2020 CU worked for you after clearing the cache? that's great to hear. Did your others users confirmed the same too?