SOLVED

Blank Custom Folder Icons in Beta 5.5.1.52665

%3CLINGO-SUB%20id%3D%22lingo-sub-709026%22%20slang%3D%22en-US%22%3EBlank%20Custom%20Folder%20Icons%20in%20Beta%205.5.1.52665%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-709026%22%20slang%3D%22en-US%22%3EAll%20my%20Whicons%20folders%20disappeared%20in%20today's%20beta%20update.%20See%20screenshot.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-710485%22%20slang%3D%22en-US%22%3ERe%3A%20Blank%20Custom%20Folder%20Icons%20in%20Beta%205.5.1.52665%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-710485%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%20thanks%20for%20your%20feedback!%20Could%20you%20please%20send%20us%20a%20screenshot%20after%20expanding%20the%20blank%20folder%3F%20%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F38320%22%20target%3D%22_blank%22%3E%40Jimmy%20Stavropoulos%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-710876%22%20slang%3D%22en-US%22%3ERe%3A%20Blank%20Custom%20Folder%20Icons%20in%20Beta%205.5.1.52665%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-710876%22%20slang%3D%22en-US%22%3EScreenshot%20attached.%3CBR%20%2F%3E%3CBR%20%2F%3EI%20use%20the%20System%20icons%2C%20but%20on%20my%20Home%20screen%2C%20I%20change%20each%20icon%20to%20be%20from%20Whicons.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-715494%22%20slang%3D%22en-US%22%3ERe%3A%20Blank%20Custom%20Folder%20Icons%20in%20Beta%205.5.1.52665%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-715494%22%20slang%3D%22en-US%22%3EThe%20latest%20build%20fixed%20my%20issue.%20Thank%20you.%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor
All my Whicons folders disappeared in today's beta update. See screenshot.
3 Replies
Highlighted

Hi, thanks for your feedback! Could you please send us a screenshot after expanding the blank folder? @Jimmy Stavropoulos 

Highlighted
Screenshot attached.

I use the System icons, but on my Home screen, I change each icon to be from Whicons.
Highlighted
Best Response confirmed by Jimmy Stavropoulos (Occasional Contributor)
Solution
The latest build fixed my issue. Thank you.