Anybody having trouble with PNG's with the new Update of Premier Pro 2018 April 3rd?

Same issues here, and nesting is not solving the problem. I updated and now have wacked out sketchy png sequences with a life of their own. They decide at will when to work fine or when to glitch out in a crazy pattern that looks like my images been hacked in the by someone in the 80s. This is really now working well for being able to deliver to clients. I guess I will re-install the old version. My trust in Adobe creating quality software I can rely upon is gone. Very frustrating and disappointing because I have loved Premiere and Adobe products for years, and now have little to no patience left. 

Yes, I'm having the same problem.  Most of my imported png files have some other weird file attached to them.  I keep trying to fix it in Photoshop but every time I reimport it does the same thing.  So frustrating.  Trying to finish my film and I have many png's in the project. 

I also am having issues. Can Adobe just fix it already? I'm irritated with updated software.

I found a work around! (that helped me at least)

I brought all my PNGs into After Effects and saved them as .MOV files with transparent backgrounds.

If you don't know how to save with transparent backgrounds, this was helpful: Quick Tip: Exporting with Alpha Channels in After Effects - The Beat: A Blog by PremiumBeat

I then brought the new MOV files into Premiere and put them in place of the PNGs. It was annoying to add the transitions all over again, but it worked! Deleting all PNGs from my project helped too. Anytime there was just one in the sequence, my whole video would render messed up. I too had a deadline today, and spent about 4 hours trying to figure out the problem. This was the best solution I could find for the time being.

I hope Adobe fixes this soon!

Haven't got time to go back though the thread to see if someone else has come up with this but the only way to fix it is to replace all of the .png files as .psd.  Finished a TVC this morning full of .png graphics and animations.  Saved them all as .psd and it's perfect.  You're not off the hook Adobe.  Still has to be fixed.  Shame!

I found this fix on an other thread:

Find the original png file in the project viewer, right click -> Modify -> Interpret Footage.

Under the Alpha Channel category, select "Conform Alpha Premultiplication To:

And also select the box: Premultiplied Alpha

Shout out to user andrewh20613583 for the fix

Yes, definitely a thing.  Brought the whole shop to a halt this morning.    We upgraded to 12.1 at close of business last night and fortunately caught it before we did a ton of work today.   Sequences with PNGs with transparency are "ghosting" and displaying over other PNGs in the timeline.   Same as described by many other posters.   However the suggestions of re-loading/shifting the in/out points did not fix the problem reliably and it would still appear at random.   If you're on deadlines like we are, Downgrading back to 12.0 is unfortunately the only way to solve this mess immediately if you can't wait for Adobe to fix.  Or I suppose another would be to go make ProRes 4444 quicktimes with alphas of all your still graphics and cut them back in.   (but then, what other bugs have we not discovered yet)

Fortunately it's not too hard to downgrade with the app manager. But if you've already converted a project and done some work in 12.1, remember you can't re-open the project in 12.0 once you downgrade.   Here is what we did to work-around on OS X:

1) BEFORE YOU DOWNGRADE... Open the new 12.1 version of your project or projects, export any sequences you have changed or created since you upgraded, --regardless of if they are currently experiencing the PNG bug--   Use "Final Cut Pro XML"

2) Then downgrade by going to the creative cloud app manager, select "installed apps" tab and where it says OPEN next to Premiere Pro, click the little arrow and choose "Other Versions" and then choose 12.0.   You need to be closed out of all your CC apps of course.

3)  For good measure we downgraded Adobe Media Encoder at the same time to 12.0 using same method.  No idea if there were bugs, but seemed like the smart play to keep these two apps matched since we rely on it a lot.

4)  Once 12.0 is reinstalled, make a brand new and fresh "rescue" project and import the XML sequences you previously exported.   If you want to rejoin them into a preexisting 12.0 project (or autosave backup)  Leave that rescue project open and open up the old projects at the same time and copy and paste those sequences where you want them.   (Note, the reason for this extra step is for some reason could not import the XML sequences directly)

5)  You'll get a new copy of the sequence and all it's related clips in your bin and will need to do some project housekeeping.  Generally the things you'll lose will depend on the complexity of your sequences, we lost some keying effects and audio stuff.  But at least we're back in action with only a few hours lost.

Hope this helps someone.  And remember, at least it's not Avid.

I have found a reproducible case and filed an internal Adobe bug. Someone will follow up on this thread. Thank you so much for reporting the issue.
Dan Ramirez
Character Animator QA

Same - On the line with them for 3 hours today. Total waste of time. They kept the claim open and just told me the senior developers were working on it. Downgraded to version 12.

Happened me today as well. And I've got a deadline. Jippiiiie!

This is really bad.