I was experiencing the exact same issue as you described, and for what I’ve found, it seems to be due to a breaking change in next@11.1.1 which is only affecting Windows.
Until this gets fixed, you can downgrade Next to version 11.1.0:
npm install next@11.1.0
yarn add next@11.1.0