SOLVED
Home

Win 10 1903 update broke OneDrive compatibility

%3CLINGO-SUB%20id%3D%22lingo-sub-836544%22%20slang%3D%22en-US%22%3EWin%2010%201903%20update%20broke%20OneDrive%20compatibility%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-836544%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20I'm%20hoping%20this%20is%20the%20right%20place%20to%20post%20%2C%20I'm%20despaired%20if%20anyone%20has%20some%20info%20in%20this%3C%2FP%3E%3CP%3EOneDrive'%20s%20shellfolder%20implementation%20is%20working%20differently%20after%20I%20updated%20to%26nbsp%3B%20win10%201903.%3C%2FP%3E%3CP%3ENow%2C%20System.StorageProviderState(Availiability%20Status)%20always%20responds%20%22Sync%20pending%22.%3C%2FP%3E%3CP%3EIt%20doesn't%20matter%20how%20you%20obtain%20the%20property%20(vb%20scripting%2C%20NET%2CC%2B%2B%2C%20getdetailsEx%2C%20IpropertyStore%3A%3AGetValue)%20it%20ALWAYS%20responds%20%22Sync%20pending%22.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBefore%201903%20it%20worked%20flawlessly%3C%2FP%3E%3CP%3EDoes%20anyone%20knows%20how%20compatibility%20is%20broken%3F%3C%2FP%3E%3CP%3Einternal%20apps%20that%20was%20looking%20for%20statue%20changes%20now%20does%20not%20work%3C%2FP%3E%3CP%3EThe%20only%20thing%20I%20can%20think%2C%20is%20going%20back%20on%20old%20Win%20version%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-836544%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAdmin%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESync%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-852650%22%20slang%3D%22en-US%22%3ERe%3A%20Win%2010%201903%20update%20broke%20OneDrive%20compatibility%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-852650%22%20slang%3D%22en-US%22%3E%3CP%3ESh*t%2C%20docs%20was%20up%20since%201703%20but%20I%20guess%20it%20was%20implemented%20in%20windows%20in%201903%2C%20I%20was%20looking%20whats%20new%20in%201903%20and%20totally%20miss%20it%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-US%2Fwindows-hardware%2Fdrivers%2Fddi%2Fcontent%2Fntifs%2Fnf-ntifs-rtlsetprocessplaceholdercompatibilitymode%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-US%2Fwindows-hardware%2Fdrivers%2Fddi%2Fcontent%2Fntifs%2Fnf-ntifs-rtlsetprocessplaceholdercompatibilitymode%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFrom%201903%20everything%20outside%20%25systemroot%25%20has%20PHCM_DISGUISE_PLACEHOLDER%20for%20default.%3C%2FP%3E%3CP%3EChanging%20it%20to%20PHCM_EXPOSE_PLACEHOLDERS%2C%26nbsp%3B%20makes%20everything%20good%2C%20and%20the%20sun%20to%20shine.%3C%2FP%3E%3CP%3EThe%20reasoning%20for%20this%20was%20that%20many%20devs%20don't%20understand%20reparse%20points.%20Can't%20argue%20there.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
VKons
New Contributor

Hi I'm hoping this is the right place to post , I'm despaired if anyone has some info in this

OneDrive' s shellfolder implementation is working differently after I updated to  win10 1903.

Now, System.StorageProviderState(Availiability Status) always responds "Sync pending".

It doesn't matter how you obtain the property (vb scripting, NET,C++, getdetailsEx, IpropertyStore::GetValue) it ALWAYS responds "Sync pending".

 

Before 1903 it worked flawlessly

Does anyone knows how compatibility is broken?

internal apps that was looking for statue changes now does not work

The only thing I can think, is going back on old Win version

1 Reply
Solution

Sh*t, docs was up since 1703 but I guess it was implemented in windows in 1903, I was looking whats new in 1903 and totally miss it

 

https://docs.microsoft.com/en-US/windows-hardware/drivers/ddi/content/ntifs/nf-ntifs-rtlsetprocesspl...

 

From 1903 everything outside %systemroot% has PHCM_DISGUISE_PLACEHOLDER for default.

Changing it to PHCM_EXPOSE_PLACEHOLDERS,  makes everything good, and the sun to shine.

The reasoning for this was that many devs don't understand reparse points. Can't argue there.

 

 

Related Conversations