woocommerce setup wizard

Hi @jacquesk01,

I understand how blocking this is, especially on a fresh install where the setup wizard should move you forward quickly, and I am keen to help get this unstuck with you. From what you shared, the error coming from core-profiler.js usually points to something in the environment or a REST API response not returning what WooCommerce expects during the onboarding flow, rather than a simple plugin conflict.

A good first step is to bypass the setup wizard entirely so you can confirm whether WooCommerce itself loads and functions correctly in your admin. You can do this by going directly to WooCommerce, Settings, and configuring the store details manually. This guide walks through all the settings covered by the wizard and how to complete them step by step outside of it: https://woocommerce.com/document/configuring-woocommerce-settings/

Given you are running PHP 8 on IIS, I would also recommend temporarily switching to PHP 8.1 or PHP 7.4 if your host allows it, then reloading the wizard or admin pages to see if the behavior changes. We have seen cases where specific server and PHP combinations affect REST responses used by the profiler.

To dig deeper and be precise, could you please share your WooCommerce System Status Report so I can review the environment in full. You can copy it from WooCommerce, Status, Get system report, and paste it into one of these services, then share the link here: https://pastebin.com, https://quickforget.com or https://gist.github.com.

Once I have that, I can check for anything specific in the server setup, REST API, or WooCommerce configuration that could explain why the profiler is failing to load.

Hi @jacquesk01,

Thank you for sharing the screenshot and your System Status Report.

The unfinished setup message typically means that WooCommerce believes some initial setup tasks weren’t fully completed via the setup wizard. Since you are manually configuring the settings, it’s safe to proceed with your setup this way. The wizard is just a guided setup and not mandatory to get WooCommerce working. Your store should function normally once all necessary settings are configured.

To clear the leftover unfinished items notification from the dashboard, you can:

• Double-check each store setup section (Payments, Shipping, Taxes, etc.) via WooCommerce → Settings to make sure you have filled in the relevant details.
• If you confirm all required settings are complete, the leftover task message might be cached or stuck due to the initial wizard error. Hiding it does the trick: https://share.zight.com/E0uQLgoY

I hope that helps. Let us know if you need anything else.

Hi @jacquesk01,

Thanks for the update and for taking the time to test a different PHP version, I can see how much effort you are putting into narrowing this down. At this stage, continuing with the manual WooCommerce setup is perfectly fine, and the unfinished tasks notice does not prevent the store from functioning once the main settings are configured, as covered here: https://woocommerce.com/document/configuring-woocommerce-settings/.

Let us wait to see how things behave after you test PHP 8.5 on Monday. Once you have feedback, share the results here and I will gladly review them and guide you on the next steps.

I will keep an eye out for your update.

Hi @jacquesk01,

I can see how persistent this has been, especially after testing multiple PHP versions and still running into the same profiler.js error. You have already covered a lot of ground here, and I want to help narrow this down as cleanly as possible.

As a next step, please try switching the site to PHP 8.3 rather than 8.5 and then reload the WooCommerce setup wizard to see if there is any change. PHP 8.3 is currently a more commonly tested version with WooCommerce and can help rule out any edge cases related to newer PHP builds.

If the error still occurs on PHP 8.3, the next thing to try is a plugin conflict test. To do this, temporarily deactivate all other plugins so that only WooCommerce is active, then attempt to run the setup wizard again. This helps confirm whether anything else in the environment is interfering with the profiler flow.

Once you have had a chance to test PHP 8.3 and the conflict check, let me know how it goes and we can take it from there.