Is the VLAN not being changed, or is it just the case that Windows is not getting a new IP address on the new VLAN? These are very different problems.
The currently released HP Provision switch code supports CoA and will successfully change the VLAN. However, clients have no way of detecting this VLAN change, and without changing IP addresses won't be able to communicate.
A future release of HP Provision code will support "port bounce". This provides the capabilty to drop link on a port at the same time the VLAN is changed, forcing the client to obtain a new IP address. Sorry, but I don't have an exact date for this code release.