"cannot acces private member" Error with Compiling C++ Projects in VScode

[sukigd]

When I try to compile a program from the Unreal Project Browser using VScode, the progress bar loads to 90% and I receive this error message:

'FHazardPointerCollection::FHazardRecord::FHazardRecord': cannot access private member declared in class 'FHazardPointerCollection::FHazardRecord'

I have all necessary C++ and C# VScode extensions, all necessary VS Build Tools C++ Development and .NET extensions, all necessary C++ and .NET SDKs and MinGW installed and set to work with VScode. I get the same error when I try to compile directly from VScode. Running either application as administrator does not help.

I have followed the steps of the official site to a tee, including directions on setting up IntelliSense with Unreal, but I am unable to generate C++ projects without incurring this error and there are no video tutorials on the matter.

Any guidance would be much appreciated! I desperately don’t want to have to use Visual Studio…

Thanks!

[Arodi007 (Pixiebell Games 💼)]

From what i seen other people with visual studio are getting the same issue as well when they update to latest version.

Failure to create a new project: "cannot access private member declared in class 'FHazardPointerCollection::FHazardRecord'"

Just to wrap up this thread you have three options. I would do them in this order if you can. Option 1: Rollback to 17.8.x in Visual Studio How To: [image] Downsides: If you did not install 17.8 you cannot roll back to it. Option 2: Update to Preview Version How To: Same as above but select “Update” Settings and select Preview instead of current. Downsides: Previews can be less stable so it may have conflicts with your particular project. (This is unlikely though) Option 3: Make t…

VS code most likely using the code as visual studio i guess, you can try an older version if that can help.

[sukigd]

Just downgraded my version and yup-- it works.

Thanks for the solution! From the discussion you sent me it does seem like it’s just an issue with the latest vs updates. Hopefully an easier solution comes along, or the UE devs patch it soon.

[Arodi007 (Pixiebell Games 💼)]

No worries

But it kinda sad, i believe it from microsoft end, they said it was fixed on 17.9 and even close the issue from Developer Community but we still having the same issue.
The staff replied with:

So it suppose to be on 17.10.

Even windows update has a broken update since january for “KB5034441” am still waiting…