Home
%3CLINGO-SUB%20id%3D%22lingo-sub-401424%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-401424%22%20slang%3D%22en-US%22%3E%3CP%3EHI%26nbsp%3B%3CSPAN%3EBrian%2C%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EDo%20you%20have%20any%20update%20for%20this%20issue%3F%26nbsp%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThank%20you.%3C%2FSPAN%3E%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-394493%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-394493%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Brian%2C%3C%2FP%3E%3CP%3Eany%20news%20on%20that%20fix%3F%3C%2FP%3E%3CP%3Ei%20have%20try%20to%20remove%20the%202%20KB%2C%20but%20the%20issue%20still%20remain...%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-390831%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-390831%22%20slang%3D%22en-US%22%3E%3CP%3ENo%20ETA%20just%20yet.%26nbsp%3B%20It%20is%20being%20worked%20on%20but%20the%20fix%20delivery%20will%20depend%20on%20the%20version%20and%20the%20delivery%20channel.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-390574%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-390574%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20any%20new%20information%20regarding%20when%20there%20will%20be%20an%20update%20that%20will%20solve%20this%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-388410%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-388410%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20problem%20in%20Sharepoint%202016%20with%20the%20swedish%20%C3%A5%C3%A4%C3%B6%20if%20they%20are%20in%20the%20filename%20(Word%2C%20excel).%20Else%20it%20works%20ok.%20Prob%20started%20after%20winupd.%20march%202019.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EProblem%20to%20open%20files%20with%20IE%20but%20not%20with%20Chrome.%20I%20have%20test%20with%20Windows%2010%20(1709)%20and%20%E2%80%9Dlatest%20and%20greatest%E2%80%9D%20versions%20of%20%26nbsp%3Bthe%20webbrowsers.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-419051%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-419051%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Everyone%20-%20and%20thanks%20for%20your%20patience.%26nbsp%3B%20We%20are%20aiming%20to%20get%20this%20into%20the%20May%20update%20for%20the%20Project%20Server%20products%20(including%20hopefully%202013)%20-%20and%20once%20we%20have%20the%20fix%20we%20will%20also%20get%20this%20to%20the%20Project%20Online%20environment.%3C%2FP%3E%0A%3CP%3EBest%20regards%2C%3C%2FP%3E%0A%3CP%3EBrian.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-419085%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-419085%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F68%22%20target%3D%22_blank%22%3E%40Brian%20Smith%3C%2FA%3EThanks%20for%20your%20reply%20on%20this!%20Just%20to%20clarify%2C%20the%20patch%20that%20will%20solve%20this%20will%20be%20available%20on%20SP%202013%20server%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-419585%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-419585%22%20slang%3D%22en-US%22%3E%3CP%3EYes%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F310308%22%20target%3D%22_blank%22%3E%40CHedman%3C%2FA%3E%20this%20will%20be%20a%20server%20side%20fix%2C%20and%20even%20though%20Project%20Server%202013%20is%20out%20of%20mainstream%20support%20this%20is%20obviously%20a%20regression%20that%20we%20need%20to%20fix.%20As%20mentioned%2C%20the%20aim%20is%20the%20May%20update%20-%20but%20we%20are%20pretty%20close%20to%20the%20deadline%20for%20getting%20this%20fix%20in.%26nbsp%3B%20I'll%20respond%20again%20next%20week%20to%20give%20an%20update%20of%20if%20we%20made%20the%20deadline.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-422916%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-422916%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20for%20the%20update%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F68%22%20target%3D%22_blank%22%3E%40Brian%20Smith%3C%2FA%3E%2C%20for%20the%20benefit%20of%20others%2C%20I%20saw%20on%20a%20LinkedIn%20group%20Brian%20mentioned%20this%20might%20end%20up%20being%20a%20Windows%20patch%20%2F%20update%20rather%20than%20Project%20working%20around%20it.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-428735%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-428735%22%20slang%3D%22en-US%22%3E%3CP%3EUninstalling%20this%20windows%20patch%20resolves%20this%20issue%20(%3CA%20href%3D%22https%3A%2F%2Fportal.msrc.microsoft.com%2Fen-US%2Fsecurity-guidance%2Fadvisory%2FCVE-2019-0784%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fportal.msrc.microsoft.com%2Fen-US%2Fsecurity-guidance%2Fadvisory%2FCVE-2019-0784%3C%2FA%3E).%20But%20avoiding%20spaces%20in%20names%20and%20such%20is%20not%20an%20easy%20answer%20when%20you%20have%20a%20couple%20of%20thousand%20active%20projects.%20Trying%20to%20decide%20between%20reversing%20the%20patch%20and%20training%20users%20to%20open%20through%20Project%20Pro%20directly%20instead.%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-428965%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-428965%22%20slang%3D%22en-US%22%3E%3CP%3EI%20would%20never%20advise%20uninstalling%20a%20security%20patch%20to%20overcome%20an%20issue%20like%20this%20Jake.%26nbsp%3B%20Also%20to%20update%20my%20earlier%20comment%20(as%20Paul%20mentioned)%20we%20are%20now%20looking%20for%20Windows%20to%20fix%20the%20root%20cause%20rather%20than%20trying%20to%20code%20around%20it%20in%20a%20Project%20Server%20patch%20-%20more%20details%20on%20timescales%20once%20I%20have%20it%20-%20but%20apologies%20for%20the%20inconvenience%20this%20bug%20is%20causing%20you%20all.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-437289%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-437289%22%20slang%3D%22en-US%22%3ESimilar%20issue%20on%20our%20side.%20See%20%3CA%20href%3D%22https%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2Fd72336df-2777-4a78-bbfa-0cfd18246eda%2Fcant-save-documents-in-library-and-folders-with-accents%3Fforum%3Dsharepointgeneral%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsocial.technet.microsoft.com%2FForums%2Fen-US%2Fd72336df-2777-4a78-bbfa-0cfd18246eda%2Fcant-save-documents-in-library-and-folders-with-accents%3Fforum%3Dsharepointgeneral%3C%2FA%3E%20Solved%20with%20latest%20IE%20update%20(11.0.120)%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-437988%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-437988%22%20slang%3D%22en-US%22%3E%3CP%20class%3D%22mentions-texteditor__content%22%20style%3D%22background-attachment%3A%20scroll%3B%20background-clip%3A%20border-box%3B%20background-color%3A%20transparent%3B%20background-image%3A%20none%3B%20background-origin%3A%20padding-box%3B%20background-position-x%3A%200px%3B%20background-position-y%3A%200px%3B%20background-repeat%3A%20repeat%3B%20background-size%3A%20auto%3B%20border-image-outset%3A%200%3B%20border-image-repeat%3A%20stretch%3B%20border-image-slice%3A%20100%25%3B%20border-image-source%3A%20none%3B%20border-image-width%3A%201%3B%20box-sizing%3A%20inherit%3B%20color%3A%20rgba(0%2C%200%2C%200%2C%200.75)%3B%20font-family%3A%20-apple-system%2Csystem-ui%2CBlinkMacSystemFont%2C%26amp%3Bquot%3B%20segoe%20ui%26amp%3Bquot%3B%2Croboto%2C%26amp%3Bquot%3Bhelvetica%20neue%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bfira%20sans%26amp%3Bquot%3B%2Cubuntu%2Coxygen%2C%26amp%3Bquot%3Boxygen%20sans%26amp%3Bquot%3B%2Ccantarell%2C%26amp%3Bquot%3Bdroid%20sans%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bapple%20color%20emoji%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bsegoe%20ui%20emoji%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bsegoe%20ui%20emoji%26amp%3Bquot%3B%2C%26amp%3Bquot%3Bsegoe%20ui%20symbol%26amp%3Bquot%3B%2C%26amp%3Bquot%3Blucida%20grande%26amp%3Bquot%3B%2Chelvetica%2Carial%2Csans-serif%3B%20font-size%3A%201.2rem%3B%20font-style%3A%20normal%3B%20font-variant%3A%20normal%3B%20font-weight%3A%20400%3B%20letter-spacing%3A%20normal%3B%20line-height%3A%201.3333%3B%20orphans%3A%202%3B%20outline-color%3A%20invert%3B%20outline-style%3A%20none%3B%20outline-width%3A%200px%3B%20text-align%3A%20left%3B%20text-decoration%3A%20none%3B%20text-indent%3A%200px%3B%20text-transform%3A%20none%3B%20vertical-align%3A%20baseline%3B%20-webkit-text-stroke-width%3A%200px%3B%20white-space%3A%20normal%3B%20word-spacing%3A%200px%3B%20padding%3A%208px%3B%20margin%3A%200px%3B%20border%3A%200px%20none%20currentColor%3B%22%3EA%20further%20update%20-%20as%20far%20as%20we%20can%20tell%20this%20ONLY%20affects%20Project%20Server%202019%2C%20assuming%20you%20are%20patched%20up%20to%20date%20on%20Project%20Server%202013%20and%202016.%26nbsp%3B%20We%20fixed%20this%20condition%20for%20Chrome%20a%20while%20back%20-%20and%20the%20recent%20Windows%20fix%20exposed%20this%20for%20other%20browsers.%26nbsp%3B%20See%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4022228%2Fdescription-of-the-security-update-for-sharepoint-server-2016%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4022228%2Fdescription-of-the-security-update-for-sharepoint-server-2016%3C%2FA%3E%20for%20Project%20Server%202016%20and%20for%202013%20-%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4032245%2Faugust-14-2018-cumulative-update-for-project-server-2013-kb4032245.%26nbsp%3B%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4032245%2Faugust-14-2018-cumulative-update-for-project-server-2013-kb4032245.%26nbsp%3B%3C%2FA%3E%20A%20more%20recent%20update%20would%20include%20these%20too.%26nbsp%3B%20Not%20sure%20when%20we%20will%20get%20the%20fix%20for%20Project%20Server%202019%2C%20but%20will%20have%20probably%20missed%20the%20May%20deadline.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-438500%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-438500%22%20slang%3D%22en-US%22%3E%3CP%3EOh%20wait....so%20Brian%20you%20say%20that%20if%20we%20are%20on%20a%20newer%20CU%20but%20on%20an%20older%20version%20of%20Project%20Server%20(eg%202013)%20that%20this%20issue%20does%20not%20occur%3F%20Thats%20good%20to%20know.%20We%20are%20a%20bit%20behind%20on%20CUs%20and%20if%20applying%20one%20of%20the%20later%20CUs%20resolves%20the%20behavior%2C%20that%20gives%20us%20added%20incentive%20to%20do%20it%20soon.%20Thanks%20for%20the%20information!!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-450715%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-450715%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Brian%2C%3C%2FP%3E%3CP%3EThanks%20for%20the%20update.%26nbsp%3B%3C%2FP%3E%3CP%3ECan%20you%20plz%20verify%2C%20after%20installing%20the%20following%20update%20my%20project%20not%20opening%20issue%20in%20Microsoft%20Professional%20will%20be%20gone.%20Btw%20I%20have%202013%20project%20server.%3C%2FP%3E%3CP%3ERemoving%20space%20of%20the%20project%20name%20is%20also%20working%2C%20but%20we%20have%20so%20many%20projects%20so%20we%20cannot%20do%20that.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-au%2Fhelp%2F4032245%2Faugust-14-2018-cumulative-update-for-project-server-2013-kb4032245%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-au%2Fhelp%2F4032245%2Faugust-14-2018-cumulative-update-for-project-server-2013-kb4032245%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20in%20Advance.%26nbsp%3B%3C%2FP%3E%3CP%3EDanish%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-451752%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-451752%22%20slang%3D%22en-US%22%3E%3CP%3EYes%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F315521%22%20target%3D%22_blank%22%3E%40Danish531%3C%2FA%3E%26nbsp%3B%2C%20my%20Project%20Server%202013%20has%20the%20latest%20patch%20and%20I%20do%20not%20see%20the%20issue.%26nbsp%3B%20This%20page%20lists%20all%20of%20the%20Project%20Server%202013%20updates%20-%26nbsp%3B%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FProject-Support-Blog%2FProject-Server-2013-Cumulative-Updates-from-2016-to-Date%2Fba-p%2F387411%22%20target%3D%22_blank%22%3Ehttps%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2FProject-Support-Blog%2FProject-Server-2013-Cumulative-Updates-from-2016-to-Date%2Fba-p%2F387411%3C%2FA%3E%3C%2FFONT%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-480886%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-480886%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Brian%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20seeing%20this%20issue%20in%20PWA%20for%20SharePoint%2FProject%20Server%202016%20(16.0.4666.1002)%20with%20MS%20Project%202016%20(16.0.10730.20264).%3C%2FP%3E%3CP%3ELooking%20forward%20to%20the%20May%20update%20!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-382867%22%20slang%3D%22en-US%22%3EProjects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-382867%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EA%20further%20update%20-%20as%20far%20as%20we%20can%20tell%20this%20ONLY%20affects%20Project%20Server%202019%2C%20assuming%20you%20are%20patched%20up%20to%20date%20on%20Project%20Server%202013%20and%202016.%26nbsp%3B%20We%20fixed%20this%20condition%20for%20Chrome%20a%20while%20back%20-%20and%20the%20recent%20Windows%20fix%20exposed%20this%20for%20other%20browsers.%26nbsp%3B%20See%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4022228%2Fdescription-of-the-security-update-for-sharepoint-server-2016%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4022228%2Fdescription-of-the-security-update-for-sharepoint-s...%3C%2FA%3E%26nbsp%3B%3CSPAN%3Efor%20Project%20Server%202016%20and%20for%202013%20-%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4032245%2Faugust-14-2018-cumulative-update-for-project-server-2013-kb4032245.%25C2%25A0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4032245%2Faugust-14-2018-cumulative-update-for-project-server...%3C%2FA%3E%3CSPAN%3E%26nbsp%3BA%20more%20recent%20update%20would%20include%20these%20too.%26nbsp%3B%20Not%20sure%20when%20we%20will%20get%20the%20fix%20for%20Project%20Server%202019%2C%20but%20will%20have%20probably%20missed%20the%20May%20deadline.%3C%2FSPAN%3E%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIf%20you%20have%20recently%20loaded%20the%20Window%20Security%20update%26nbsp%3B%3CFONT%20style%3D%22background-color%3A%20%23ffffff%3B%22%3E%3CA%20href%3D%22https%3A%2F%2Fportal.msrc.microsoft.com%2Fen-US%2Fsecurity-guidance%2Fadvisory%2FCVE-2019-0784%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fportal.msrc.microsoft.com%2Fen-US%2Fsecurity-guidance%2Fadvisory%2FCVE-2019-0784%3C%2FA%3E%3C%2FFONT%3E%20and%20are%20not%20able%20to%20open%20certain%20projects%20from%20the%20Project%20Center%20then%20check%20if%20the%20project%20name%20contains%20a%20space.%26nbsp%3B%20We%20are%20investigating%20and%20hopefully%20will%20soon%20get%20a%20fix%20for%20this%2C%20but%20depending%20which%20part%20we%20need%20to%20fix%20(client%2C%20server%20or%20service)%20it%20could%20take%20a%20while%20before%20it%20is%20available%20in%20an%20update%20or%20your%20distribution%20channel.%26nbsp%3B%20There%20are%20workarounds%20-%20you%20can%20still%20open%20just%20fine%20by%20opening%20the%20client%20Project%20application%20and%20then%20File%2C%20Open%20to%20select%20the%20project%2C%20or%20you%20could%20just%20rename%20the%20plan%20and%20remove%20the%20space(s).%26nbsp%3B%20Personally%20I%20try%20and%20avoid%20using%20spaces%20and%20other%20special%20characters%20in%20project%20names%2C%20and%20of%20course%20spaces%20are%20supported%20and%20should%20work%2C%20but%20occasionally%20they%20can%20trip%20something%20up%20unexpectedly%20-%20like%20this%20recent%20change.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-382867%22%20slang%3D%22en-US%22%3E%3CP%3E%3CSPAN%3EA%20further%20update%20-%20as%20far%20as%20we%20can%20tell%20this%20ONLY%20affects%20Project%20Server%202019%2C%20assuming%20you%20are%20patched%20up%20to%20date%20on%20Project%20Server%202013%20and%202016.%26nbsp%3B%20We%20fixed%20this%20condition%20for%20Chrome%20a%20while%20back%20-%20and%20the%20recent%20Windows%20fix%20exposed%20this%20for%20other%20browsers.%26nbsp%3B%20See%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4022228%2Fdescription-of-the-security-update-for-sharepoint-server-2016%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4022228%2Fdescription-of-the-security-update-for-sharepoint-s...%3C%2FA%3E%26nbsp%3B%3CSPAN%3Efor%20Project%20Server%202016%20and%20for%202013%20-%26nbsp%3B%3C%2FSPAN%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4032245%2Faugust-14-2018-cumulative-update-for-project-server-2013-kb4032245.%25C2%25A0%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4032245%2Faugust-14-2018-cumulative-update-for-project-server...%3C%2FA%3E%3CSPAN%3E%26nbsp%3BA%20more%20recent%20update%20would%20include%20these%20too.%26nbsp%3B%20Not%20sure%20when%20we%20will%20get%20the%20fix%20for%20Project%20Server%202019%2C%20but%20will%20have%20probably%20missed%20the%20May%20deadline.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-TEASER%3E%3CLINGO-SUB%20id%3D%22lingo-sub-562522%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-562522%22%20slang%3D%22en-US%22%3E%3CP%3EHey%20Brian%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20any%20update%20on%20this%20please.%20I%20am%20particular%20interested%20in%202013%20on%20Prem%20please.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-562538%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-562538%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Lee-Anne%2C%3C%2FP%3E%0A%3CP%3EWith%20the%20latest%20patches%20for%20the%20server%20and%20client%20it%20is%20resolved%2C%20we%20recently%20patch%20a%202013%20on-premises%20customer%20with%20April%202019%20CU%20Server%20update%20and%20April%202019%20client%20update%20and%20it%20was%20resolved%20for%20them.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EPaul%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-565361%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-565361%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Paul%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20can%20you%20provide%20links%20to%20the%20latest%20update%20articles%20%3F%20I%20need%20to%20cross%20reference%20with%20what%20our%20organistion%20has%20rolled%20out%20today%20as%20we%20still%20appear%20to%20have%20the%20same%20issue%20as%20before%20for%20Project%20Server%202016%20(on-prem)%3B%20PWA%20refuses%20to%20open%20MS%20Project%20client%20with%20spaces%20and%20Windows%20Explorer%20won't%20open%20from%20the%20ribbon%20in%20a%20document%20library.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMS%20Project%20(O365)%2016.0.10730.20264%3C%2FP%3E%3CP%3ESharePoint%202016%20KB4018293%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks.%2C%20Steve%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-565369%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-565369%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4495300%2Fapril-2019-updates-for-microsoft-office%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4495300%2Fapril-2019-updates-for-microsoft-office%3C%2FA%3E%26nbsp%3Bhas%20all%20the%20April%20updates%20-%20or%20the%20May%20server%20updates%20are%20due%20out%20tomorrow%20Steve.%3C%2FP%3E%0A%3CP%3EBest%20regards%2C%3C%2FP%3E%0A%3CP%3EBrian%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-636371%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-636371%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Brian%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIs%20there%20any%20update%20on%20the%20May%20updates%20please%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThank%20you%20%26amp%3B%20regards%3C%2FP%3E%3CP%3EHelen%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-636372%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-636372%22%20slang%3D%22en-US%22%3E%3CP%3EI%20updated%20the%202016%20and%202019%20Project%20and%20Project%20Server%20postings%20in%20this%20Project%20Support%20blog%20with%20the%20May%20updates%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F342866%22%20target%3D%22_blank%22%3E%40Helen87%3C%2FA%3E%26nbsp%3B-%20all%20details%20here%20too%20-%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4501270%2Fmay-2019-updates-for-microsoft-office%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4501270%2Fmay-2019-updates-for-microsoft-office%3C%2FA%3E%3C%2FP%3E%0A%3CP%3EBest%20regards%2C%3C%2FP%3E%0A%3CP%3EBrian.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-644024%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-644024%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3Ei'm%20still%20having%20problems%20with%20this.%20I'm%20using%20Project%20Pro%202016%20with%20Project%20server%202013.%20I%20patched%20the%20server%20to%20May's%20update%20and%20also%20my%20win%2010%20client%20has%20the%20latest%20windows%20update.%20I%20was%20still%20seeing%20the%20error%20in%20Project%20pro%20so%20i%20update%20this%20to%20the%20latest%20update%20and%20now%20it%20doesn't%20attempt%20to%20open%20the%20plan.%3C%2FP%3E%3CP%3EAre%20there%20still%20issues%3F%3C%2FP%3E%3CP%3EKind%20Regards%3C%2FP%3E%3CP%3ECarl%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-657433%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-657433%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Brian%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20for%20getting%20back%20to%20me.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20a%20client%20who%20is%20not%20on%20Project%20Server%20but%20is%20still%20experiencing%20the%20issue.%20I%20cannot%20reproduce%20the%20error%20myself%20and%20cannot%20determine%20why%20they%20would%20still%20be%20experiencing%20this%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20input%20would%20be%20much%20appreciated%20-%20thank%20you%20very%20much%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-658299%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-658299%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F342866%22%20target%3D%22_blank%22%3E%40Helen87%3C%2FA%3E%26nbsp%3B%20-%20when%20you%20say%20they%20are%20not%20on%20Project%20Server%20-%20I%20assume%20you%20mean%20they%20are%20opening%20an%20mpp%20file%20from%20a%20Url%20maybe%3F%26nbsp%3B%20This%20issue%20was%20specific%20to%20Project%20Server%2C%20but%20I%20guess%20if%20a%20file%20with%20a%20space%20stored%20on%20SharePoint%20didn't%20get%20encoded%20that%20might%20give%20a%20similar%20problem.%26nbsp%3B%20Can%20you%20confirm%20the%20exact%20repro%20of%20the%20problem%20and%20the%20versions%20of%20SharePoint%20and%20browsers%20involved%3F%3C%2FP%3E%0A%3CP%3EThanks%2C%3C%2FP%3E%0A%3CP%3EBrian.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-724855%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-724855%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20there%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20anyone%20know%20if%20the%20KB4464600%20for%20Project%202013%20%2B%20SP%20is%20fixing%20the%20issue%20that%20I%20cannot%26nbsp%3Bopen%20Projects%20directly%26nbsp%3Bfrom%20the%20WebApp%20under%20certain%20cirumstances%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBest%20regards%2C%3C%2FP%3E%3CP%3ERaxacid%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-842768%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-842768%22%20slang%3D%22en-US%22%3E%3CP%3EHi%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F68%22%20target%3D%22_blank%22%3E%40Brian%20Smith%3C%2FA%3E%26nbsp%3B%2C%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20have%20same%20problem%20in%20Project%20Server%202016%2C%20after%20installation%20of%20%22%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-us%2Fhelp%2F4022228%2Fdescription-of-the-security-update-for-sharepoint-server-2016%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EJuly%202018%20SharePoint%20update%3C%2FA%3E%22%26nbsp%3Bwhich%20resolved%20our%20issue%20(Project%20with%20spaces%20open%20in%20all%20browsers)%20but%20we%20are%20facing%20another%20new%20issue%20in%20all%20OOB%20SharePoint%20lists%20after%20that%20patch.%20Below%20is%20the%20screenshot.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20style%3D%22width%3A%20400px%3B%22%3E%3CIMG%20src%3D%22https%3A%2F%2Fgxcuf89792.i.lithium.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F130623i4D695C283E8B831F%2Fimage-size%2Fmedium%3Fv%3D1.0%26amp%3Bpx%3D400%22%20alt%3D%22clipboard_image_0.png%22%20title%3D%22clipboard_image_0.png%22%20%2F%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3EThen%20I%20have%20applied%20%22%3CA%20href%3D%22https%3A%2F%2Fsupport.microsoft.com%2Fen-ae%2Fhelp%2F4464549%2Fdescription-of-the-security-update-for-sharepoint-enterprise-server%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%20noopener%20noreferrer%22%3EMay%202019%20SharePoint%20security%20update%3C%2FA%3E%22%20but%20still%20same.%20So%20we%20revert%20it%20back%20all%20the%20updates.%20Now%20we%20are%20on%20same%20stage%20%22%3CSPAN%3Eproject%20name%20contains%20a%20space%20not%20opening%20with%20MS%20Project%3C%2FSPAN%3E%22.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3EHaseeb%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-853636%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-853636%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20just%20ran%20full%20patching%20on%20all%20SP16%20servers%20(first%20time%20in%2018%20months%20!)%20and%20we%20have%20the%20functionality%20back%20to%20open%20MS%20Project%20from%20Project%20Server.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-856077%22%20slang%3D%22en-US%22%3ERe%3A%20Projects%20with%20spaces%20in%20their%20names%3F%20A%20recent%20Windows%20Security%20update%20could%20cause%20issues!%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-856077%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F387740%22%20target%3D%22_blank%22%3E%40steved0115%3C%2FA%3E%26nbsp%3B%2C%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Microsoft

A further update - as far as we can tell this ONLY affects Project Server 2019, assuming you are patched up to date on Project Server 2013 and 2016.  We fixed this condition for Chrome a while back - and the recent Windows fix exposed this for other browsers.  See https://support.microsoft.com/en-us/help/4022228/description-of-the-security-update-for-sharepoint-s... for Project Server 2016 and for 2013 - https://support.microsoft.com/en-us/help/4032245/august-14-2018-cumulative-update-for-project-server... A more recent update would include these too.  Not sure when we will get the fix for Project Server 2019, but will have probably missed the May deadline.

 

 

If you have recently loaded the Window Security update https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0784 and are not able to open certain projects from the Project Center then check if the project name contains a space.  We are investigating and hopefully will soon get a fix for this, but depending which part we need to fix (client, server or service) it could take a while before it is available in an update or your distribution channel.  There are workarounds - you can still open just fine by opening the client Project application and then File, Open to select the project, or you could just rename the plan and remove the space(s).  Personally I try and avoid using spaces and other special characters in project names, and of course spaces are supported and should work, but occasionally they can trip something up unexpectedly - like this recent change.  

30 Comments
Regular Visitor

We have problem in Sharepoint 2016 with the swedish åäö if they are in the filename (Word, excel). Else it works ok. Prob started after winupd. march 2019.

 

Problem to open files with IE but not with Chrome. I have test with Windows 10 (1709) and ”latest and greatest” versions of  the webbrowsers.

Regular Visitor

Hi

 

Is there any new information regarding when there will be an update that will solve this?

Microsoft

No ETA just yet.  It is being worked on but the fix delivery will depend on the version and the delivery channel.

Occasional Visitor

Hi Brian,

any news on that fix?

i have try to remove the 2 KB, but the issue still remain...

Thanks

 

Visitor

HI Brian,

Do you have any update for this issue? 

 

Thank you.

 

 

Microsoft

Hi Everyone - and thanks for your patience.  We are aiming to get this into the May update for the Project Server products (including hopefully 2013) - and once we have the fix we will also get this to the Project Online environment.

Best regards,

Brian.

Regular Visitor

@Brian SmithThanks for your reply on this! Just to clarify, the patch that will solve this will be available on SP 2013 server?

Microsoft

Yes @CHedman this will be a server side fix, and even though Project Server 2013 is out of mainstream support this is obviously a regression that we need to fix. As mentioned, the aim is the May update - but we are pretty close to the deadline for getting this fix in.  I'll respond again next week to give an update of if we made the deadline.

Thanks for the update @Brian Smith, for the benefit of others, I saw on a LinkedIn group Brian mentioned this might end up being a Windows patch / update rather than Project working around it.

Regular Visitor

Uninstalling this windows patch resolves this issue (https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0784). But avoiding spaces in names and such is not an easy answer when you have a couple of thousand active projects. Trying to decide between reversing the patch and training users to open through Project Pro directly instead.  

Microsoft

I would never advise uninstalling a security patch to overcome an issue like this Jake.  Also to update my earlier comment (as Paul mentioned) we are now looking for Windows to fix the root cause rather than trying to code around it in a Project Server patch - more details on timescales once I have it - but apologies for the inconvenience this bug is causing you all.

Occasional Contributor
Similar issue on our side. See https://social.technet.microsoft.com/Forums/en-US/d72336df-2777-4a78-bbfa-0cfd18246eda/cant-save-doc... Solved with latest IE update (11.0.120)
Microsoft

A further update - as far as we can tell this ONLY affects Project Server 2019, assuming you are patched up to date on Project Server 2013 and 2016.  We fixed this condition for Chrome a while back - and the recent Windows fix exposed this for other browsers.  See https://support.microsoft.com/en-us/help/4022228/description-of-the-security-update-for-sharepoint-s... for Project Server 2016 and for 2013 - https://support.microsoft.com/en-us/help/4032245/august-14-2018-cumulative-update-for-project-server... A more recent update would include these too.  Not sure when we will get the fix for Project Server 2019, but will have probably missed the May deadline.

Regular Visitor

Oh wait....so Brian you say that if we are on a newer CU but on an older version of Project Server (eg 2013) that this issue does not occur? Thats good to know. We are a bit behind on CUs and if applying one of the later CUs resolves the behavior, that gives us added incentive to do it soon. Thanks for the information!!

Visitor

Hi Brian,

Thanks for the update. 

Can you plz verify, after installing the following update my project not opening issue in Microsoft Professional will be gone. Btw I have 2013 project server.

Removing space of the project name is also working, but we have so many projects so we cannot do that. 

 

https://support.microsoft.com/en-au/help/4032245/august-14-2018-cumulative-update-for-project-server...

 

Thank in Advance. 

Danish

Microsoft

Yes @Danish531 , my Project Server 2013 has the latest patch and I do not see the issue.  This page lists all of the Project Server 2013 updates - https://techcommunity.microsoft.com/t5/Project-Support-Blog/Project-Server-2013-Cumulative-Updates-f... 

Frequent Visitor

Hi Brian,

 

We are seeing this issue in PWA for SharePoint/Project Server 2016 (16.0.4666.1002) with MS Project 2016 (16.0.10730.20264).

Looking forward to the May update !

Occasional Visitor

Hey Brian, 

 

Is there any update on this please. I am particular interested in 2013 on Prem please. 

 

Thanks

Hi Lee-Anne,

With the latest patches for the server and client it is resolved, we recently patch a 2013 on-premises customer with April 2019 CU Server update and April 2019 client update and it was resolved for them.

 

Paul

Frequent Visitor

Hi Paul,

 

Please can you provide links to the latest update articles ? I need to cross reference with what our organistion has rolled out today as we still appear to have the same issue as before for Project Server 2016 (on-prem); PWA refuses to open MS Project client with spaces and Windows Explorer won't open from the ribbon in a document library.

 

MS Project (O365) 16.0.10730.20264

SharePoint 2016 KB4018293

 

Thanks., Steve

Microsoft

https://support.microsoft.com/en-us/help/4495300/april-2019-updates-for-microsoft-office has all the April updates - or the May server updates are due out tomorrow Steve.

Best regards,

Brian

Regular Visitor

Hi Brian,

 

Is there any update on the May updates please?

 

Thank you & regards

Helen

Microsoft

I updated the 2016 and 2019 Project and Project Server postings in this Project Support blog with the May updates @Helen87 - all details here too - https://support.microsoft.com/en-us/help/4501270/may-2019-updates-for-microsoft-office

Best regards,

Brian.

Occasional Visitor

Hi,

i'm still having problems with this. I'm using Project Pro 2016 with Project server 2013. I patched the server to May's update and also my win 10 client has the latest windows update. I was still seeing the error in Project pro so i update this to the latest update and now it doesn't attempt to open the plan.

Are there still issues?

Kind Regards

Carl

Regular Visitor

Hi Brian,

 

Thanks for getting back to me.

 

We have a client who is not on Project Server but is still experiencing the issue. I cannot reproduce the error myself and cannot determine why they would still be experiencing this error.

 

Any input would be much appreciated - thank you very much

 

 

Microsoft

Hi @Helen87  - when you say they are not on Project Server - I assume you mean they are opening an mpp file from a Url maybe?  This issue was specific to Project Server, but I guess if a file with a space stored on SharePoint didn't get encoded that might give a similar problem.  Can you confirm the exact repro of the problem and the versions of SharePoint and browsers involved?

Thanks,

Brian.

Occasional Visitor

Hi there

 

Does anyone know if the KB4464600 for Project 2013 + SP is fixing the issue that I cannot open Projects directly from the WebApp under certain cirumstances?

 

Best regards,

Raxacid

 

  

Regular Visitor

Hi @Brian Smith , 

 

We have same problem in Project Server 2016, after installation of "July 2018 SharePoint update" which resolved our issue (Project with spaces open in all browsers) but we are facing another new issue in all OOB SharePoint lists after that patch. Below is the screenshot.

 

clipboard_image_0.png

Then I have applied "May 2019 SharePoint security update" but still same. So we revert it back all the updates. Now we are on same stage "project name contains a space not opening with MS Project". 

 

Regards,

Haseeb

 

Visitor

Hi All,

 

We just ran full patching on all SP16 servers (first time in 18 months !) and we have the functionality back to open MS Project from Project Server.

 

Regards.

Regular Visitor

Thanks @steved0115 ,